|Handling typedef in the Roslind C++ parser firstname.lastname@example.org (1992-05-18)|
|From:||email@example.com (Michael Stal)|
|Organization:||Siemens AG, Munich, W-Germany|
|Date:||Mon, 18 May 1992 08:22:41 GMT|
I am currently planning to develop a C++ information abstractor (i.e. a
C++-parser, that extracts detailed information about classes and variables
from C++-sources). For this purpose I want to use the Unix-tools yacc and
lex together with the well known Roskind-grammar. Some questions arise:
- Can anybody provide me with an idea or solution how to cope with the
TYPEDEFname/IDENTIFIER-problem within the scanner?
As far as I've found out, a symbol table is not enough. In some
cases right context must be analyzed additionally. It's very
interesting, that the scanner of the GNU g++-compiler is not
generated with flex but hand-crafted instead. Maybe this was caused
by the same problem (?!).
- Is there any C++-parser (at least C++ v2.1) available in source code,
which solves the problem?
- Are there any alternatives to using yacc/lex/Roskind-grammar for
developing commercial C++-parsers?
Thank you very much for all help
ZFE BT SE 31
8000 Muenchen 83
Tel: + 49 89 636 49 380
Return to the
Search the comp.compilers archives again.