Re: Syntax diagram driven parser

vbdis@aol.com (VBDis)
12 Oct 2000 22:33:36 -0400

          From comp.compilers

Related articles
[12 earlier articles]
Re: Syntax diagram driven parser irobot@swbell.net (Brian Webb) (2000-10-01)
Re: Syntax diagram driven parser vbdis@aol.com (2000-10-01)
Re: Syntax diagram driven parser vbdis@aol.com (2000-10-08)
Re: Syntax diagram driven parser vbdis@aol.com (2000-10-08)
Re: Syntax diagram driven parser aaron1000@webtv.net (2000-10-08)
Re: Syntax diagram driven parser joachim_d@gmx.de (Joachim Durchholz) (2000-10-10)
Re: Syntax diagram driven parser vbdis@aol.com (2000-10-12)
| List of all articles for this month |

From: vbdis@aol.com (VBDis)
Newsgroups: comp.compilers
Date: 12 Oct 2000 22:33:36 -0400
Organization: AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com
References: 00-10-070
Keywords: parse

"Joachim Durchholz" <joachim_d@gmx.de> schreibt:
>Hmmm... you'd have to parse the imported module as well to gain that
>information. Or learn how to decipher the format of compiled Delphi
>modules.


I followed both ways, and found deciphering DCU files is somewhat
safer and faster than another parse of the source code. In most cases
the locations of the DCU files are known, in contrast to the source
file locations. And sometimes no source files are available at all, or
contain incompatible information. Just the SYSTEM.PAS file, which is
implicitly included into any Delphi source file, contains some C-style
struct declarations, instead of Delphi-conforming record declarations!


The DCU file parser also revealed, that the Delphi compilers work
context-sensitive. Many records in a DCU file can be interpreted
correctly only, when their context is known.


DoDi


Post a followup to this message

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