|Parser email@example.com (Aaron Becher) (2002-09-12)|
|Re: Parser firstname.lastname@example.org (Christian Lindig) (2002-09-12)|
|Re: Parser email@example.com (Karsten Nyblad) (2002-09-12)|
|Re: Parser firstname.lastname@example.org (Fred J. Scipione) (2002-09-14)|
|Re: Parser email@example.com (Grzegorz Jakacki) (2002-09-14)|
|Re: Parser firstname.lastname@example.org (VBDis) (2002-09-14)|
|Re: Parser email@example.com (Mikael 'Zayenz' Lagerkvist) (2002-09-19)|
|From:||"Fred J. Scipione" <firstname.lastname@example.org>|
|Date:||14 Sep 2002 00:16:57 -0400|
|Posted-Date:||14 Sep 2002 00:16:56 EDT|
"Aaron Becher" <email@example.com> wrote in message
> What would be the best approach? I have a VERY large pool of source
> code that needs a certain line of code inserted at the beginning of
> every function (a macro). A few years ago, I created from scratch a
> tool that could parse our C and C++ source code and insert and/or
> maintain this line of code at the beginning of every
> function. However, it does run into problems now and then, especially
> when our coding standard is not followed.
Adrian Johnstone's RDP package has a "C" pretty printer grammar
which you might try adapting to your purpose. It might also point
to a direction for adapting the Roskind "C++" grammar as well.
Return to the
Search the comp.compilers archives again.