Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "André Pönitz" <andre.poenitz@nokia.com>
To: gdb@sourceware.org
Subject: Re: GDB frontends, MI-speak and object notation
Date: Thu, 28 May 2009 13:57:00 -0000	[thread overview]
Message-ID: <200905281557.37805.andre.poenitz@nokia.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA077E6FF0@ecamlmw720.eamcs.ericsson.se>

On Thursday 28 May 2009 15:31:42 Marc Khouzam wrote:
> 
> > I wonder how other front-end developers handle GDB/MI output messages.
> > In the code I'm working on, regular expressions are used to parse MI
> > messages and extract certain values from them. This is pretty
> > straightforward to write, but doesn't seem to fully use the
> > <structuredness> of MI-speak, and lacks the spirit of MI. I'm 
> > reviewing
> > means of mapping MI (which seems to be a subset of JSON with a few
> > cosmetic differences and exceptions) to object-like 
> > structures so I can
> > work with it on a higher level. Has anyone had similar ideas?
> 
> Yes, in Eclipse we parse the MI output into a hierarchy of classes
> following the MI specification.  I agree with you that using
> regular expression is loosing the value of MI.

Same for Qt Creator. And I also think that regular expressions
is not a good long-term solution.

Andre'


  reply	other threads:[~2009-05-28 13:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 12:00 Dmitry Dzhus
2009-05-28 13:32 ` Marc Khouzam
2009-05-28 13:57   ` André Pönitz [this message]
2009-05-29  9:25     ` Dmitry Dzhus
2009-05-29 15:30       ` Marc Khouzam
2009-05-30 16:44 ` Dmitry Dzhus
2009-05-30 19:24   ` Vladimir Prus
2009-05-30 21:27   ` Tom Tromey

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=200905281557.37805.andre.poenitz@nokia.com \
    --to=andre.poenitz@nokia.com \
    --cc=gdb@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