From: "Eli Zaretskii" <eliz@gnu.org>
To: Paul Hilfinger <hilfingr@gnat.com>
Cc: gdb-patches@sources.redhat.com, drow@false.org, jimb@redhat.com
Subject: Re: [RFA]: Turn on Ada support, take 2
Date: Thu, 17 Jun 2004 17:48:00 -0000 [thread overview]
Message-ID: <3405-Thu17Jun2004204518+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040617052451.C85DBF2D16@nile.gnat.com> (message from Paul Hilfinger on Thu, 17 Jun 2004 01:24:51 -0400 (EDT))
> From: Paul Hilfinger <hilfingr@gnat.com>
> Date: Thu, 17 Jun 2004 01:24:51 -0400 (EDT)
> >
> > If you feel strongly about this, I won't object to use of @t{'Address}
> > in those cases where you think the standard markup looks bad.
>
> Eli,
>
> Well, I feel strongly that the result of @code{'Address} looks really
> cruddy in an .info file. However, it occurs to me that if I rewrote
> the section a little to supply dummy prefixes (e.g., @code{Obj'Address}),
> the result would not be so bad and would use the right markup command.
If @code{Obj'Address} would look natural for Ada users, please use
that. Otherwise, @t{'Address} is okay wherever you need it.
next prev parent reply other threads:[~2004-06-17 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 9:08 [RFA]: Turn on Ada support Paul Hilfinger
2004-06-08 22:15 ` Eli Zaretskii
2004-06-09 9:23 ` Paul Hilfinger
2004-06-09 18:25 ` Eli Zaretskii
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 [this message]
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
2004-08-11 10:42 [RFA]: Turn on Ada support, take 2 Paul Hilfinger
2004-08-11 23:08 ` 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=3405-Thu17Jun2004204518+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.com \
--cc=jimb@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