improving the debugger for kdevelop 4??

[jbb]

Good work

But...
Given that we can already parse gdb output what is the advantage of using MI?

Pro
. MI should be stable across future versions
. IIRC it has mixed source and assembly output
. fill in the blanks here

Con
. MI has changed from it's early versions, why think it won't in the future? 
(the cynic in me :-)
. It's not human readable.
. It's a bit of work (but not huge)
. fill in the blanks here

Most (if not all) of the features that people want are really to do with the 
UI not with parsing the output. (tool tips is the most obvious)

Can you tell us why this will help us? I'm not against doing this but it just 
seems unnecessary which is why I've not bothered. Note that thinking this 
could be fun to do _is_ a valid reason :-)

jbb

On Fri, 02 Apr 2004 20:30, Roberto Raggi wrote:
> Hi!
>
> a few days ago I've discovered the new GDB/MI interface of gdb
> (info:/gdb/gdb/mi).. the new GDB/MI interface seems very easy to parse, so
> maybe we can replace/extend the gdb parser in our debugger with something
> new!! anyway, I wrote a small *prototype* for a GDB/MI parser(please, find
> it in attachment to this email. it is less than 8KB), so at least we can
> start to investigate ;)
>
> ciao robe