From: Eli Zaretskii <eliz@gnu.org>
To: Mihail Zenkov <mihail.zenkov@gmail.com>
Cc: brobecker@adacore.com, mihail.zenkov@gmail.com,
tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: D language support
Date: Wed, 28 Apr 2010 17:10:00 -0000 [thread overview]
Message-ID: <83iq7by04i.fsf@gnu.org> (raw)
In-Reply-To: <20100428025334.69e28794.mihai.zenkov@gmail.com>
> Date: Wed, 28 Apr 2010 02:53:34 +0300
> From: Mihail Zenkov <mihail.zenkov@gmail.com>
> Cc: Mihail Zenkov <mihail.zenkov@gmail.com>, tromey@redhat.com, gdb-patches@sourceware.org
>
> gdb/NEWS:
> * D language support.
> Support for debugging the D programming language has been
> integrated into GDB.
Suggest to say this instead:
GDB now supports debugging programs written in the D programming
language.
> gdb/doc/ChangeLog:
> * gdb.texinfo: Add mention about D language support.
The ChangeLog entry should include the name(s) of node(s) added to the
manual.
> +@cindex D
> +Support for D is partial. For information on D, see
> +@ref{D,,D}.
Please remove the @cindex entry from here. You already have one in
the section where the D support is described; having another identical
index entry pointing here, where D is not described at all, is not
useful. The index entries are for readers who are looking for a
description of some specific subject, so they should point to the place
where that subject is described in full.
> +@value{GDBN} can be used to debug programs written in D and compiled with
> +GDC, LDC or DMD.
Suggest to add "compilers" to the end of this sentence. Also, please
leave two spaces between sentences.
> Currently @value{GDBN} supports only one D specific
> +feature - dynamic arrays.
^
Please use "---" (3 dashes in a row) to produce an em-dash.
Okay with those changes.
Thanks.
next prev parent reply other threads:[~2010-04-28 17:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 23:57 Mihail Zenkov
2009-12-30 12:56 ` Joel Brobecker
2010-01-09 6:25 ` Mihail Zenkov
2010-01-09 6:29 ` Mihail Zenkov
2010-01-09 14:23 ` Joel Brobecker
2010-01-13 4:42 ` Mihail Zenkov
2010-01-15 5:10 ` Joel Brobecker
2010-01-15 21:02 ` Tom Tromey
2010-01-15 21:05 ` Tom Tromey
2010-04-14 22:22 ` Mihail Zenkov
2010-04-20 21:39 ` Tom Tromey
2010-04-21 0:01 ` Mihail Zenkov
2010-04-21 15:57 ` Joel Brobecker
2010-04-22 0:11 ` Mihail Zenkov
2010-04-22 0:44 ` Joel Brobecker
2010-04-22 1:53 ` Mihail Zenkov
2010-04-23 18:11 ` Tom Tromey
2010-04-24 0:06 ` Mihail Zenkov
2010-04-27 16:05 ` Joel Brobecker
2010-04-27 23:55 ` Mihail Zenkov
2010-04-28 15:17 ` Joel Brobecker
2010-04-28 17:11 ` Eli Zaretskii
2010-04-29 2:16 ` Mihail Zenkov
2010-04-28 17:10 ` Eli Zaretskii [this message]
2010-04-29 1:59 ` Mihail Zenkov
2010-04-29 3:10 ` Eli Zaretskii
2010-04-29 14:47 ` Joel Brobecker
2010-04-23 18:09 ` Tom Tromey
2010-04-23 20:15 ` Leandro Lucarella
2010-04-23 20:37 ` Tom Tromey
2010-04-26 23:51 ` Stan Shebs
2010-04-27 0:29 ` Joel Brobecker
2010-04-23 21:35 ` Robert Clipsham
2010-04-24 0:26 ` Mihail Zenkov
2010-04-27 20:27 ` Robert Clipsham
-- strict thread matches above, loose matches on Subject: below --
2009-08-17 23:02 Mihail Zenkov
2009-08-18 4:18 ` Eli Zaretskii
2009-08-18 16:39 ` Tom Tromey
[not found] ` <20090818225844.GA9879@homero.springfield.home>
2009-08-19 18:36 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83iq7by04i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mihail.zenkov@gmail.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox