[antlr-interest] new book organization question
Terence Parr
parrt at cs.usfca.edu
Wed Aug 20 11:52:36 PDT 2008
On Aug 20, 2008, at 8:27 AM, Monty Zukowski wrote:
> The flow between subsystems is by far the most difficult part of my
> ANTLR parsers/analyzers/code generators to explain to new hires. I've
> found it very helpful to take a single expression and show what is
> happening with it in each phase. I also have a summary document which
> gives the conceptual flow through the system and what files are
> involved in each phase.
That makes a lot of sense.
> A changeset has been quite a useful tool to show which files need to
> be modified when altering the entire system, such as when adding a new
> built-in type, which, in my system, affects the lexer for adding a new
> imaginary node, some support files which deal with type coercion, some
> java files which represent our program structure, and the string
> template for code generation. We use trac as our bug tracking system
> and it's quite easy to link to any committed changeset and it shows a
> nice html diff.
Cool. I think fisheye does this too :)
Thanks!
Ter
More information about the antlr-interest
mailing list