From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drow@false.org, dirk.behme@googlemail.com, gdb@sourceware.org
Subject: Re: MI return error changed from 6.3 to 6.4?
Date: Sat, 08 Apr 2006 10:07:00 -0000 [thread overview]
Message-ID: <17463.29399.957570.820724@farnswood.snap.net.nz> (raw)
In-Reply-To: <uy7yg60jy.fsf@gnu.org>
...
> > Manual> This mechanism is provided as an aid to developers of GDB/MI
> > Manual> clients and not as a reliable interface into the CLI. Since the
> > Manual> command is being interpreteted in an environment that assumes
> > Manual> GDB/MI behaviour, the exact output of such commands is likely to
> > Manual> end up being an un-supported hybrid of GDB/MI and CLI output.
> >
> > so maybe we shouldn't fix it.
>
> Alternatively, we could leave what manual says as it is now, and fix
> the code. Note that it says that _existing_ CLI commands are
> accepted. So perhaps we should detect non-existing commands and
> return an MI error indication.
I seem to also recall that Andrew also said that using CLI through MI was a
temporary arrangement (although I can't find that in the manual).
> > On the other hand this was written before the command -interpreter-exec.
> > If entering CLI commands directly (using -interpreter-exec implicitly)
> > can be made as reliable as using -interpreter-exec explicitly, maybe this
> > would be a convenient alternative, and the above paragraph could be
> > removed from the manual.
>
> Such an incompatible change would require a quarantine period during
> which the CLI support in MI is marked deprecated.
What's incompatible? I mean in addition to, not instead of and here I'm
suggesting the opposite i.e that CLI support in MI is not deprecated. My
feeling is that -interpreter-exec *does* provide a reliable interface into the
CLI while the hack that was used in GDB 6.3 didn't. I'm just saying that we
may as well use it access CLI directly from MI. First though I think we
should formally document the syntax of MI and CLI commands so that they don't
get confused. CLI commands seem to always start with a lower case letter
while MI commands start with "-" (I see TUI uses "-" to mean scroll backward).
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-04-08 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 16:02 Dirk Behme
2006-04-07 17:36 ` Daniel Jacobowitz
2006-04-08 8:23 ` Nick Roberts
2006-04-08 9:57 ` Eli Zaretskii
2006-04-08 10:07 ` Nick Roberts [this message]
2006-04-08 18:35 ` Eli Zaretskii
2006-04-08 18:45 ` Nick Roberts
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=17463.29399.957570.820724@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=dirk.behme@googlemail.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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