From: Eli Zaretskii <eliz@is.elta.co.il>
To: Jim Ingham <jingham@apple.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: add set cp-abi command
Date: Tue, 09 Apr 2002 22:33:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020410092346.20549H-100000@is> (raw)
In-Reply-To: <B80D7663-4C19-11D6-B08E-000393540DDC@apple.com>
On Tue, 9 Apr 2002, Jim Ingham wrote:
> I got distracted from this for a little while... Here is a final
> version with something in the texi file as well.
Thanks. Some comments about the doco patch:
> + @kindex set cp-abi
> + @item set cp-abi
> + @itemx set cp-abi auto
> + Set the C++ ABI that gdb will use to decode C++ objects. The default is "auto"
> + which means gdb will assume the gnu-v2 ABI unless it sees symbols that
> + look like the gnu-v3 ABI, in which case it will switch to the gnu-v3 ABI. With
> + no arguments, list the available C++ ABIs.
Please explain in a few words what "ABI" means; I don't think Joe Random
C++ User will necessarily know that. A list of possible values one can
use (in addition to "auto") is also something the manual should have.
(Btw, I think that the built-in documentation of the "set abi" command
could also use a word of explanation of the term "ABI".)
Please change "auto" to ``auto'' (this looks much prettier in the printed
version, and is translated into "auto" in the Info output), and please
use C@t{++} instead of C++ (also for aesthetic reasons).
Finally, we use `@value{GDBN}' instead of just `gdb' throughout the
manual (evidently to allow custom versions of manuals for GDB that is
named differently).
next prev parent reply other threads:[~2002-04-10 5:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 10:56 Jim Ingham
2002-03-13 12:11 ` Eli Zaretskii
2002-03-13 12:11 ` Daniel Jacobowitz
2002-03-14 13:14 ` Jim Ingham
2002-03-14 13:26 ` Daniel Jacobowitz
2002-03-15 15:53 ` Jim Ingham
2002-03-15 19:41 ` Daniel Jacobowitz
2002-03-18 12:01 ` Jim Ingham
2002-03-20 15:19 ` Daniel Jacobowitz
2002-03-20 19:02 ` Jim Ingham
2002-03-22 10:34 ` Daniel Jacobowitz
2002-03-22 11:04 ` Andrew Cagney
2002-03-22 11:09 ` Daniel Jacobowitz
2002-03-22 11:29 ` Jim Ingham
2002-04-09 17:27 ` Jim Ingham
2002-04-09 17:54 ` Daniel Jacobowitz
2002-04-10 11:10 ` Jim Ingham
2002-04-10 11:58 ` Daniel Jacobowitz
2002-04-09 22:33 ` Eli Zaretskii [this message]
2002-04-10 11:14 ` Jim Ingham
2002-04-11 12:25 ` Eli Zaretskii
2002-03-15 17:11 ` Jim Ingham
2002-03-14 15:29 ` Andrew Cagney
2002-03-15 10:33 ` Jim Ingham
2002-03-15 17:29 ` 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=Pine.SUN.3.91.1020410092346.20549H-100000@is \
--to=eliz@is.elta.co.il \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jingham@apple.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