|Info needed on implementing Java compiler email@example.com (Esben Krag Hansen) (1998-05-12)|
|Re: Info needed on implementing Java compiler Bronikov@inreach.com (Dima Bronnikov) (1998-05-15)|
|Re: Info needed on implementing Java compiler firstname.lastname@example.org (1998-05-15)|
|From:||Dima Bronnikov <Bronikov@inreach.com>|
|Date:||15 May 1998 22:33:37 -0400|
Feel free to disregard my advice since my work is not finished, but I
ended up blatantly reading in all tokens capturing classes (including
nested ones) before feeding tokens to parser. Don't remember the exact
gotcha, but Sun's nested classes made me on this one.
The other thing (pretty much obvious) is that since access to class
member may textually precede definition of the class, it necessary to
leave method bodies and fields init expressions processing until after
all classes in file have been parsed and signatures of all members in
all classes are known.
If you plan to use yacc, consider the grammar in comp.compiler archive,
it's also available (there have been two minor additions) at my page
Esben Krag Hansen wrote:
> I need information on implementing a Java compiler, with specifics such as
> symbol table management, type-checking, abstract syntax, problems
> encountered, etc. References to papers would be great.
Return to the
Search the comp.compilers archives again.