Re: Parser

"VBDis" <vbdis@aol.com>
14 Sep 2002 16:16:10 -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: "VBDis" <vbdis@aol.com>
Newsgroups: comp.compilers
Date: 14 Sep 2002 16:16:10 -0400
Organization: AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com
References: 02-09-078
Keywords: translator
Posted-Date: 14 Sep 2002 16:16:10 EDT

"Aaron Becher" <aaron.becher@eds.com> schreibt:


>[Using a regular parser in a rewrite tool is usually an exercise in
>frustration, because the parser throws away info that you'd want to
>keep in the rewritten source code. C is particularly unpleasant in
>this regard because compilers generally start by expanding the
>preprocessor stuff, then compile the expanded stuff, by which time
>it's pretty much impossible to reconstruct the source. My experience
>is that regular expression pattern matching combined with ad-hoc
>heuristics give about as good result as any. -John]


Currently I'm marking all procedures manually, and let my maintenance
tool look only for these marks. The marks must be inserted only once
into an source file, and the error rate in non-standard code should
not exceed the error rate of automated processing without human
review.


DoDi

Post a followup to this message

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