[antlr-interest] yet more thoughts on error handling / recovery

[Monty Zukowski]

> I don't like burdening all calls to match() with an extra parameter, 
> but users of ANTLR can optimize by simply changing the code generator 
> to not include this position parameter and then provide a different 
> match() method. I just looked at the C output (non exception handling 
> version) to see how many parameters there were to the match 
> routine...lots! Check this out:
> _zzmatch(3, &zzBadText, &zzMissText, &zzMissTok, &zzBadTok, &zzMissSet)

Remember the possibility of having this all in a struct, possibly 
including the parse stack to be able to make re-entrant parsers.  
Wouldn't that be handy for UI's if you could save off the parse to a 
certain point and then just pick up there repeatedly to interactively 
parse?  Man, I hope I get some serious time to play with that.  
Continuations for parsers.  With C actions.  Oh yeah!

Monty

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/