MI async status output

Terekhov, Mikhail mikhail.terekhov@emc.com
Fri Apr 18 20:39:00 GMT 2014

> -----Original Message-----
> From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
> Behalf Of Vladimir Prus
> Sent: Friday, April 18, 2014 12:43 PM
> To: Bob Rossi
> Cc: Andrew Burgess; gdb@sourceware.org
> Subject: Re: MI async status output
> On 18.04.2014 20:30, Bob Rossi wrote:
> >
> > The solution to these problems is pretty clear, lets give developers an API.
> I am not sure what's different between "API" and GDB/MI, which is also an
> API or some sort. No matter what a new API might be, the problems of GDB
> changes and supporting multiple versions of GDB will be the same, except for
> wrong grammar. Web developers have the same problems with API changes,
> for all I know.

The difference is very important - in case of grammar the only way to verify that GDB
really follows it is to write and maintain complete set of test cases while in case of API
compiler will do it for you automatically. The situation with MI clearly shows that and
JSON will be no different in this regard. That doesn't mean that there is no need to
verify that this API works correctly of course :}


More information about the Gdb mailing list