From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: show inferior-tty
Date: Mon, 11 Jul 2005 21:28:00 -0000 [thread overview]
Message-ID: <17106.58567.662569.830805@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050711131032.GC25755@nevyn.them.org>
> Yes. I asked Bob to do this. The set of values accessible by -gdb-set
> is not documented in the MI section of the manual; we generally treat
> them as part of the CLI. The example for -gdb-set shows $foo, which is
> a convenience or "internal" variable, not a setting [although the
> example for -gdb-show does show annotate...].
>
> I don't think incorporating the values controllable by -gdb-set in a
> stable interface is a good idea for compatibility.
Other MI commands, notably those used for program control exec-run, exec-next
etc, also implemented through CLI commands (although they are called in a
different way). I'm not sure where -gdb-set would fail (asynchronous
operation?). If its not a good idea to use -gdb-set, perhaps it should be
removed or, at least, a note added to the manual as Konstantin Karganov
suggested. Alternatively, perhaps it could be implemented so that it
doesn't use CLI (like -inferior-tty-set?) It seems wasteful to implement
a separate MI command for each show subcommand.
Nick
next prev parent reply other threads:[~2005-07-11 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 2:13 Nick Roberts
2005-07-11 3:32 ` Bob Rossi
2005-07-11 13:10 ` Daniel Jacobowitz
2005-07-11 21:28 ` Nick Roberts [this message]
2005-07-12 2:07 ` Nick Roberts
2005-07-12 11:41 ` Bob Rossi
2005-07-12 13:34 ` Nick Roberts
2005-07-12 14:07 ` Dave Korn
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=17106.58567.662569.830805@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).