From: "Eli Zaretskii" <eliz@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: MI and backwards compatibility
Date: Sun, 03 Oct 2004 15:02:00 -0000 [thread overview]
Message-ID: <01c4a904$Blat.v2.2.2$9a9c14a0@zahav.net.il> (raw)
In-Reply-To: <20041002172449.GE5224@white> (message from Bob Rossi on Sat, 2 Oct 2004 13:24:49 -0400)
> Date: Sat, 2 Oct 2004 13:24:49 -0400
> From: Bob Rossi <bob@brasko.net>
> Cc: gdb@sources.redhat.com
>
> If for example the -break-list command in the MI3 protocol becomes
> incompatible with the -break-list command that was in the MI2 protocol,
> and the MI version is bumped from 2 to 3 because of it,
>
> * will -break-list be left around for old front ends that use MI2 and a
> new MI command -break-list-new be created for front ends that use MI3?
>
> * will -break-list act differently in MI2 mode than it will for MI3
> mode?
>
> or the very bad broken case,
>
> * will -break-list act the new way in both MI2 and MI3 mode?
It should be the second alternative. If the first alternative were
true, we wouldn't need to bump the MI version.
> I have a gut feeling that the last case is the case GDB currently acts
> like, and this is what I am worried about.
Shouldn't happen, but if you have examples to the contrary, let's hear
them.
> Is the documentation distributed with each version?
Yes, each GDB distribution includes the documentation.
> BTW, I think it would be helpful to put the information on this thread
> in the MI doco, so that front end developers understand the compatibility
> philosophy of GDB's MI interface.
I don't think it would be a good idea to point people at a mailing
list thread. What we normally do is when some piece of information
like what is discussed in this thread sounds important to have in the
docs, we add the information itself to gdbint.texinfo or some other
relevant documentation file.
> Finally, thanks for the responding quickly!
You are welcome.
next prev parent reply other threads:[~2004-10-03 4:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 14:25 Bob Rossi
2004-10-02 16:26 ` Bob Rossi
2004-10-02 17:06 ` Eli Zaretskii
2004-10-03 4:53 ` Bob Rossi
2004-10-03 15:02 ` Eli Zaretskii [this message]
2004-10-03 16:39 ` Bob Rossi
2004-10-02 16:28 ` Eli Zaretskii
2004-10-02 16:38 ` Bob Rossi
2004-10-02 17:24 ` Eli Zaretskii
2004-10-05 19:41 ` Andrew Cagney
2004-10-06 1:01 ` Daniel Jacobowitz
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='01c4a904$Blat.v2.2.2$9a9c14a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=bob@brasko.net \
--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).