This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [PATCH] Hooks still needed for annotations
- From: Bob Rossi <bob at brasko dot net>
- To: Nick Roberts <nickrob at snap dot net dot nz>, gdb-patches at sources dot redhat dot com
- Date: Thu, 30 Jun 2005 20:20:52 -0400
- Subject: Re: [PATCH] Hooks still needed for annotations
- References: <17053.24737.153388.915345@farnswood.snap.net.nz> <20050601113004.GC15414@white> <17054.10607.109160.333076@farnswood.snap.net.nz> <20050603190856.GB32722@nevyn.them.org> <17056.56022.36723.292491@farnswood.snap.net.nz> <20050603235923.GA9992@nevyn.them.org> <20050604130228.GA24976@white> <20050613031400.GF9288@nevyn.them.org>
> > Also, I think it's reasonable to say that GDB should have a parser that
> > FE's can use. The only way to have a parser that can be tested properly
> > is to allow it to be packaged and tested in GDB's testsuite. Otherwise,
> > if the annotations are removed, FE's like GVD, XXGDB, DDD, KGDB, ...
> > are either going to "go the way of the bison" or they are going to have
> > to write code that handles GDB/MI. Do we really want 5-10 GDB/MI
> > parser's out there (each with there own bugs)?
>
> This is also unrelated to the removal of annotations.
>
> I don't much think a parser is GDB's responsibility. Offering one as a
> convenience, sure, maybe. Note that a lot of frontends won't get to
> use it anyway! If we ship it with GDB, then it's going to be covered
> under the GPL.
The more I think of it, the more I feel that I am correct on this. Even
if the parser was under the GPL, proprietary projects (Apple?) could
simply use the parse tree to translate the data into a nice format of
there own (XML?) and then communicate that to a parser thats linked into
there application. This type of solution would allow a closed source
company to get the benefits of an MI parser/semantical analyzer,
contribute to the project, and not have to think 1 second about low
level MI stuff in there FE.
Bob Rossi