Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:doco] Zap mi1 reference
Date: Mon, 16 Feb 2004 23:27:00 -0000	[thread overview]
Message-ID: <403151D2.1060908@gnu.org> (raw)
In-Reply-To: <20040213203704.GA654@white>

> On Fri, Feb 13, 2004 at 03:05:06PM -0500, Andrew Cagney wrote:
> 
>> Hello,
>> 
>> This removes a reference to "mi1" in the documentation.  It's no longer 
>> tested (hence 'supported').
> 
> 
> I don't really know how I feel about dropping support for old mi
> versions. Is that the plan for future versions of mi?

Well, neither can GDB support broken parts of the interface indefinitly :-(

The vague intent is to slowly phase in fixes while at the same time 
phasing out the testing and eventually the code for the old interfaces. 
  This should give a separate ui writer a year or so of grace with any 
specific MI version.

This goes with the assumption that separate UI authors are qualifying 
their interface against a specific GDB/MI version.

> I think the MI functions should be backwards compatible. Are they?

Theory or reality?  In theory the output is largely upward compatible - 
code can discard unrecognized fields.  In reality warts eventually start 
to appear.  For instance, both:
- using frame ID's with varobj
- N:M breakpoints
will impact significantly on the MI interface.

Andrew



  reply	other threads:[~2004-02-16 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 20:05 Andrew Cagney
2004-02-13 20:37 ` Bob Rossi
2004-02-16 23:27   ` Andrew Cagney [this message]
2004-02-16 23:41     ` Bob Rossi
2004-02-17 19:00       ` Andrew Cagney
2004-02-14 11:34 ` Eli Zaretskii
2004-02-16 23:17   ` Andrew Cagney
2004-02-17  7:06     ` Eli Zaretskii
2004-02-17 14:55       ` Andrew Cagney

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=403151D2.1060908@gnu.org \
    --to=cagney@gnu.org \
    --cc=bob@brasko.net \
    --cc=gdb-patches@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