From: "André Pönitz" <apoenitz@trolltech.com>
To: gdb-patches@sourceware.org
Subject: Re: [patch] MI: breakpoint "script" is a LIST
Date: Sun, 16 Nov 2008 08:23:00 -0000 [thread overview]
Message-ID: <200811152349.27767.apoenitz@trolltech.com> (raw)
In-Reply-To: <gfh94m$e85$1@ger.gmane.org>
On Thursday 13 November 2008 14:12:54 Vladimir Prus wrote:
> Jan Kratochvil wrote:
>
> > Hi,
> >
> > Nemiver could not parse the MI2 output. The list of commands is a `list', not
> > a `tuple'.
>
> For how long this bug is here? Is the risk that existing frontend break higher than
> inconvenience to keep the code as is?
To be honest, I'd expect existing "frontend implementors" to be able to parse
"MI" output that's not conforming to the specs rather well as problems like
the one mentioned here are not exactly unheard of ;-}
So I am personally all for rectifying the situation and produce "proper MI2
output" from now on, just for the sake of coming generations...
Andre'
prev parent reply other threads:[~2008-11-15 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 15:11 Jan Kratochvil
2008-11-13 15:35 ` Vladimir Prus
2008-11-13 15:39 ` Jan Kratochvil
2008-11-13 20:21 ` Vladimir Prus
2008-11-13 21:35 ` Tom Tromey
2008-11-13 21:55 ` Marc Khouzam
2008-11-13 21:59 ` Jan Kratochvil
2008-11-16 8:23 ` André Pönitz [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=200811152349.27767.apoenitz@trolltech.com \
--to=apoenitz@trolltech.com \
--cc=gdb-patches@sourceware.org \
/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