probably the best C++ parser...

Steven T. Hatton hattons at
Tue Jul 5 13:09:09 UTC 2005

On Friday 01 July 2005 11:01, Alexander Neundorf wrote:
> can find is gcc, but did you know gccxml
> ( ? It's basically the real gcc, but
> it doesn't produce machine instructions, but an xml file describing the
> source file.
> So you get
> -all functions
> -all variables
> -all parameters for functions
> -the locations where the functions are declared (file and line number)
> etc. in a machine-readable format.
> I think this could be really useful for kdevelop (go to
> declaration/definition, completion, parameter info, etc.) Did anybody
> already play with it ?
> Btw. it's written by the same guys who develop cmake :-)
> Bye
> Alex

I don't believe there is a need for a new parser.  Roberto has put a lot of 
work into r++.  Is there some reason no to use it?  Perhaps I'm not 
understanding what people are wanting.

I will confess that I don't really understand the current code representations 
in KDevelop.  The class browser calls its code model a DOM, but I have come 
to wonder if that should be understood in terms of the W3C DOM.  My guess is 
that it is structurally very close.  If so, perhaps using the existing 
infrastructure would be more prudent.  It could probably be enhanced to 
provide whatever other XML-DOM features we might want.

Bear in mind that working with XML tools does not necessitate the existence of 
actual XML.  For example, an XML-DOM instance could be built programmatically 
without ever creating a single XML element in text from.

More information about the KDevelop-devel mailing list