Re: C/C++ front-end extension a la SWIG?

[Daniel Berlin <dan at cgsoftware dot com>]

> 
> I rather strongly disagree -- at least if we're talking about the
> future.
> 
> The G++ parser will always be very useful for one thing: parsing the
> code the same way that G++ does.  For example, one can imagine hooking
> it into GDB so that you could type C++ expressions at GDB for
> interpretation; GDB would use the G++ front-end to parse the
> expression, and then interpret the tree structure.

I've looked at doing this before, to fix a few p roblems with the gdb
expression evaluator.
The parser is too much of a mess, no offense.

< A source-browser
> designed to work with G++ could use the G++ parser, and be sure to
> handle G++ extensions and bugs just like G++.
>

Same here, except the parser is also too slow for my taste.
> As the parser itself (in the sense of the bison bits) are replaced
> (and they will be, they will be) then this will become even more
> useful.

I agree here.
Please, for the love of god, replace the parser.
> 
> There is no reason the G++ front-end cannot be as useful in the free
> software community as the EDG front-end has been in other communities,
> for example.

I wait for the day.
> 
> --
> Mark Mitchell                   mark@codesourcery.com
> CodeSourcery, LLC               http://www.codesourcery.com
>