From: Andrew Cagney <cagney@gnu.org>
To: gdb@sources.redhat.com
Subject: GDB's command qualifier character is `/'
Date: Sun, 19 Oct 2003 16:50:00 -0000 [thread overview]
Message-ID: <3F92C0D2.6050807@gnu.org> (raw)
This seems to keep comming up, sigh!
GDB's CLI, long ago established `/' as its command qualifier character vis:
x/i
display/i
print/x
GDB's user base is very familar with this syntax(1) so adding new
qualfiers using this syntax would provide a consistent user experience
(if there is x/i, how come there isn't "info break/l"?).
In fact, in the case of all these specific commands (including "info
break/l") trying to switch to UNIX's option syntax vis:
x --i
would be a disaster!
What's unfortunate in all this is that the current CLI code doesn't
directly parse the qualifier convention. For instance:
(gdb) x<TAB>
x/i x/b x/8 x/4
and
(gdb) load/vma /lma
(load, using vma addresses, the file "/lma").
If the command doesn't involve files, though, I can't think of a reason
for not using the `/' qualifier. If it does involve files, then I guess
the work needed to add the qualifier will need to include modifing the
cli.
Note that this doesn't address "parameterized qualifiers" (tar/dump
convention?) and "qualified parameters" (not allowed?).
enjoy,
Andrew
(1) Personally, I'm always using the `/' qualifier, but I can't remember
when, if ever, I used one of the UNIX style command options.
next reply other threads:[~2003-10-19 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 16:50 Andrew Cagney [this message]
2003-10-20 0:32 ` Daniel Jacobowitz
2003-10-21 19:29 ` Andrew Cagney
2003-10-22 9:56 ` Andreas Schwab
2003-10-22 14:38 ` Andrew Cagney
2003-10-20 21:54 ` Jim Blandy
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=3F92C0D2.6050807@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.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