|looking for a c++ -> c++ parser firstname.lastname@example.org (1998-11-15)|
|Re: looking for a c++ -> c++ parser email@example.com (1998-11-19)|
|Re: looking for a c++ -> c++ parser firstname.lastname@example.org (Eric Marsden) (1998-11-19)|
|Re: looking for a c++ -> c++ parser email@example.com (David Chase) (1998-11-24)|
|From:||firstname.lastname@example.org (Greg Lindahl)|
|Date:||19 Nov 1998 23:26:38 -0500|
|Organization:||a guest of Shadow Island Games|
> [Parsing C++ is so painful, particularly in programs that use #define, that
> I expect that ad-hoc partial parsing would work better than full parsing.
#define isn't a problem -- in this instance the writer didn't seem to
want to get human-readable source back, so you can just run the thing
through cpp first. Parsing C++ _is_ painful, but the EDG parser source
is available free for non-commercial use, and I heard (a while ago)
about a project by Kathy Lindlan <email@example.com> to build
some stuff with the EDG parser which allows tool builders to do
interesting things to parsed C++ programs. Details are at:
I'm not sure if there is a tool which takes her IL and outputs C++,
but that part doesn't look hard.
Return to the
Search the comp.compilers archives again.