From: Eli Zaretskii <eliz@is.elta.co.il>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: fnf@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: "maint print type" should print all the flag bits
Date: Tue, 11 Dec 2001 00:18:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1011211101713.19L-100000@is> (raw)
In-Reply-To: <nppu5m248u.fsf@zwingli.cygnus.com>
On 10 Dec 2001, Jim Blandy wrote:
> > > The "maint print type" command does not print all the flag
> > > bits.
> >
> > This command is not documented in the manual. Could someone please
> > fill that void?
>
> Are the other `maint' commands documented in the manual?
At least some of them are. Try "i maint TAB" in Info, and you will
see which ones are there.
> They're only meant for use by GDB developers.
How do you expect the GDB developers to discover their existence if
they aren't documented? Even if they do discover their existence, how
would a developer who never used a particular command know what it
does? The built-in doc strings are terse and don't explain much. For
example, suppose i use "maint print type" and see it print
TYPE_FLAG_TARGET_STUB--how do I figure out what that means? (If you
think that GDB's sources explain that clearly, think again ;-)
I think every command should be documented in the manual.
next prev parent reply other threads:[~2001-12-11 8:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-09 11:14 Fred Fish
2001-12-09 19:08 ` Jim Blandy
2001-12-10 1:03 ` Eli Zaretskii
2001-12-10 12:44 ` Jim Blandy
2001-12-11 0:18 ` Eli Zaretskii [this message]
[not found] ` <3C162900.288B@redhat.com>
2001-12-11 9:21 ` Eli Zaretskii
2001-12-11 10:59 ` Andrew Cagney
2001-12-11 11:44 ` Daniel Jacobowitz
2001-12-11 17:47 ` Andrew Cagney
2001-12-11 19:14 ` Daniel Jacobowitz
2001-12-12 0:29 ` Eli Zaretskii
2001-12-12 0:29 ` Eli Zaretskii
2001-12-11 10:55 ` Jim Blandy
2001-12-11 11:16 ` Stan Shebs
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.1011211101713.19L-100000@is \
--to=eliz@is.elta.co.il \
--cc=fnf@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.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