From: Daniel Jacobowitz <dan@codesourcery.com>
To: Dave Korn <dave.korn.cygwin@googlemail.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
Subject: Re: Turnaround upgrade in mi2
Date: Sun, 10 Jan 2010 21:09:00 -0000 [thread overview]
Message-ID: <20100110210902.GA5665@caradoc.them.org> (raw)
In-Reply-To: <4B4A1DAA.1030006@gmail.com>
On Sun, Jan 10, 2010 at 06:34:18PM +0000, Dave Korn wrote:
> I have a vague memory that the difference is how asynchronous output from
> the inferior is presented in the output stream, and that the difference was
> enough to make it impossible to unambiguously parse an mi stream without
> knowing which one you were dealing with in advance. Sorry, I have no
> reference, but I'm sure there was a sane reason, I think it was to do with the
> output format and its parseability, and so it wouldn't have been just because
> new commands were added.
Yes. There were also some fixes to existing commands, like using a
tuple instead of a list. It had nothing to do with new commands.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2010-01-10 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 16:03 Sean Chen
2010-01-10 17:39 ` Vladimir Prus
2010-01-10 18:17 ` Dave Korn
2010-01-10 21:09 ` Daniel Jacobowitz [this message]
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=20100110210902.GA5665@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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