From: Andrew Cagney <cagney@gnu.org>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: MI changes
Date: Fri, 24 Sep 2004 22:43:00 -0000 [thread overview]
Message-ID: <4154A265.6090607@gnu.org> (raw)
In-Reply-To: <20040923123307.GA989@white>
> Hi,
>
> Could I please have a response to this topic? I am being held up on the
> development of my project while waiting for this decision.
I think others have already responded to this proposal with a clear
rationale for not making a change. We've already got numeric prefixes
which are returned with the command result. Asynchronous output has to
be self contained.
Andrew
> I propose several changes to MI.
>
> 1. Every MI output command is prefixed with a label saying what type
> of command it is. This is easy for synchronous commands. We will have
> to make a list of asynchronous MI output commands that can be
> documented some where.
>
> benefit: the front end knows how to deal with the data it was
> given in all circumstances
>
> 2. Because of this new label, all MI output commands of it's type
> will be backwards compatible. Only adding fields and such things are
> allowed. If it is necessary to change the command, a new MI command
> and label will be put in it's place.
>
> benefit: front ends will be very reliable because they will work
> with new and old GDB's. They will also work with snapshot of GDB
> instead of only major releases.
>
> BTW, this Email does not address MI input commands in any way. This will
> be the next step on my list.
>
> Thanks,
> Bob Rossi
>
next prev parent reply other threads:[~2004-09-24 22:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 12:33 Bob Rossi
2004-09-24 22:43 ` Andrew Cagney [this message]
2004-09-25 0:44 ` Bob Rossi
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=4154A265.6090607@gnu.org \
--to=cagney@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