Jim Idle wrote:
> This may well be a safe point that I missed and I will look at it,
> but I suspect it only works with your rule formulation.
Thanks.
> It is not a good idea to use backtracking though unless your input is
>  always guaranteed to be correct, as otherwise the ability to give
> good error messages is pretty much destroyed.
Well, we got this even with "backtracking = false;" as a grammar option
(the specific symptom being that some rule functions were being entered,
but not leaving via the codepath that did rulePostProcessing).

Richard

List: http://www.antlr.org/mailman/listinfo/antlr-interest
Unsubscribe: 
http://www.antlr.org/mailman/options/antlr-interest/your-email-address

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"il-antlr-interest" group.
To post to this group, send email to il-antlr-interest@googlegroups.com
To unsubscribe from this group, send email to 
il-antlr-interest+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/il-antlr-interest?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to