> You have to be more specific with the lexer here if you want that kind of
> behavior
I don't get why?
The ANTLR book mentions auto-backtracking (which seems to be what is
*not* happening here), and which can be turned on with "options
{backtrack=true;}"
Would that not solve this problem?
If so, are there any issues (aside from performance) that might be a
reason not to have this turned on?
It certainly seems a general approach of "take the easy path, then
optimise proven slow parts, as required" is more favourable than
adding this complexity.
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/il-antlr-interest?hl=en.
