From: "Eli Zaretskii" <eliz@gnu.org>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Turn on Ada support
Date: Wed, 09 Jun 2004 18:25:00 -0000 [thread overview]
Message-ID: <9003-Wed09Jun2004204544+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040609092355.AA07EF2956@nile.gnat.com> (message from Paul Hilfinger on Wed, 9 Jun 2004 05:23:55 -0400 (EDT))
> From: Paul Hilfinger <hilfingr@gnat.com>
> Date: Wed, 9 Jun 2004 05:23:55 -0400 (EDT)
> >
> > What else can B be in this context?
>
> A function name. I take it "function or file @var{B}" is too terse for you?
No, I simply missed that, sorry.
> > This should say "as of @value{GDBN} version X.YY". A year or two from
> > now, someone will have hard time updating this verbiage given the
> > changes in Ada support.
>
> OK, but I am not sure what editorial comment you are implying with the
> word "verbiage" (:->).
A bad way to say "wording"... ;-)
> > > +The type of the @t{'Address} attribute may not be @t{System.Address}.
> >
> > I think you should use @code instead of @t in this and similar cases.
>
> Umph. The problem is that @code{'Address} generates `'Address' in Info files,
> which looks odd.
That's true, but isn't that a problem in all Ada-related
documentation?
next prev parent reply other threads:[~2004-06-09 18:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 9:08 Paul Hilfinger
2004-06-08 22:15 ` Eli Zaretskii
2004-06-09 9:23 ` Paul Hilfinger
2004-06-09 18:25 ` Eli Zaretskii [this message]
2004-06-10 9:40 ` Paul Hilfinger
2004-06-09 7:24 ` Jim Blandy
2004-06-09 9:40 ` Paul Hilfinger
2004-06-09 13:12 ` Daniel Jacobowitz
2004-06-09 13:40 ` Andrew Cagney
2004-06-09 16:21 ` Jim Blandy
2004-06-10 9:50 ` Paul Hilfinger
2004-06-16 8:42 ` [RFA]: Turn on Ada support, take 2 Paul Hilfinger
2004-06-16 18:07 ` Eli Zaretskii
2004-06-17 5:24 ` Paul Hilfinger
2004-06-17 17:48 ` Eli Zaretskii
2004-06-16 8:34 ` [PATCH]: Further updates to ada-* files Paul Hilfinger
2004-06-27 0:10 ` Andrew Cagney
2004-06-27 8:56 ` Paul Hilfinger
2004-06-28 14:47 ` Andrew Cagney
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=9003-Wed09Jun2004204544+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.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