[antlr-interest] Re: Compiler design workflow - any suggestions?
Monty Zukowski
monty at codetransform.com
Tue May 4 22:46:00 PDT 2004
On May 4, 2004, at 5:05 PM, lgcraymer wrote:
> Actually, what Ter's parse tree approach provides is stepwise
> derivation output. It's an elegant way of getting canonical output
> which is useful for analysis. I've extended it to tree grammars and
> am pretty pleased with the results. It is true that refactoring will
> change the output, but that could be fixed with a comparison tool;
> manual analysis is less cumbersome than you would think. Also,
> derivation output is a good step in determining line coverage for
> grammars. We need to devise some support tools, but I really do
> believe that we have finally hit upon the right path for grammar
> testing.
>
Yeah, I can see that's really useful. Separate the parsing from the
tree building or actions. "What is that parser actually doing?!?!?" is
a common question.
Monty Zukowski
ANTLR & Java Consultant -- http://www.codetransform.com
ANSI C/GCC transformation toolkit --
http://www.codetransform.com/gcc.html
Embrace the Decay -- http://www.codetransform.com/EmbraceDecay.html
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/antlr-interest/
<*> To unsubscribe from this group, send an email to:
antlr-interest-unsubscribe at yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
More information about the antlr-interest
mailing list