public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: MI and backwards compatibility
Date: Sat, 02 Oct 2004 16:38:00 -0000	[thread overview]
Message-ID: <20041002162822.GD5224@white> (raw)
In-Reply-To: <01c4a89c$Blat.v2.2.2$40bcdc20@zahav.net.il>

On Sat, Oct 02, 2004 at 06:23:08PM +0200, Eli Zaretskii wrote:
> > Date: Fri, 1 Oct 2004 10:25:17 -0400
> > From: Bob Rossi <bob@brasko.net>
> > 
> > So, here is an example that I don't see to far fetched within the next
> > few years. The question is, what does backwards compatibility mean?
> > This is what I expect,
> > 
> > FE 1.0 or after to never work with GDB 1.0
> > FE 1.0 to work with GDB 2.0 on using mi2.
> > FE 2.0 to work with GDB 2.0 and 3.0 using mi2
> >            and with GDB 4.0 on with mi3
> > FE 3.0 to work with GDB 2.0 and 3.0 using mi2
> >            and with GDB 4.0 with mi3
> >            and with GDB 5.0 with mi4
> 
> I don't see any problems with what you described.  Am I missing
> something?

Are you saying that the goal of GDB is to be backwards compatible with
old MI protocols? That is a simple question that i am asking.

If so, I need the documentation of all of these protocols. I need to
know how to implement an MI1 protocol, MI2 protocol, ...

Thanks,
Bob Rossi

  reply	other threads:[~2004-10-02 16:28 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
2004-10-03 16:39         ` Bob Rossi
2004-10-02 16:28 ` Eli Zaretskii
2004-10-02 16:38   ` Bob Rossi [this message]
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=20041002162822.GD5224@white \
    --to=bob@brasko.net \
    --cc=eliz@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).