Re: Parser

"Fred J. Scipione" <fjscipio@rochester.rr.com>
14 Sep 2002 00:16:57 -0400

          From comp.compilers
Related articles
Parser aaron.becher@eds.com (Aaron Becher) (2002-09-12)
Re: Parser lindig@eecs.harvard.edu (Christian Lindig) (2002-09-12)
Re: Parser knyblad@baan.com (Karsten Nyblad) (2002-09-12)
Re: Parser fjscipio@rochester.rr.com (Fred J. Scipione) (2002-09-14)
Re: Parser jakacki@hotmail.com (Grzegorz Jakacki) (2002-09-14)
Re: Parser vbdis@aol.com (VBDis) (2002-09-14)
Re: Parser d00-mla@nada.kth.se (Mikael 'Zayenz' Lagerkvist) (2002-09-19)
| List of all articles for this month |
From: "Fred J. Scipione" <fjscipio@rochester.rr.com>
Newsgroups: comp.compilers
Date: 14 Sep 2002 00:16:57 -0400
Organization: Road Runner
References: 02-09-078
Keywords: translator
Posted-Date: 14 Sep 2002 00:16:56 EDT

"Aaron Becher" <aaron.becher@eds.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.
....<snip>...


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.

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.