Oh! Sorry! i wrote it wrongly. I meant a set of actions, which will get
executed during look aheads in semantic predicates and syntactic predicates.
But Jim, i am not able to understand you.
Jim :Can’t rollback as it isn’t a database and track state isn’t really the
right thing to be doing here
What i meant by rollback is something like an action which will get executed
after we find out the predicate matching is not possible. For example if i
do a LA(n), say at some point, there is a conflict and it requires the
context to resolve the conflict. setting the context while executing the
LA(n) and resetting the context in a rollback action(something the user
should provide). Please bear with me, if you have already understood that.
Jim : nor is tracing what rule you came through to influence parsing really,
though scopes are better
Can you give a small example, of how to set a flag using scope while doing a
LA(n)? Thanks...
Jim : {{ action executes even if in synpred/backtrack }}
Please point me to the relevant doc. I am not understanding this. I find
that the syntactic predicates don't execute actions of the rules they are
matching.
Thanks,
Gokul.
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.
