At 14:23 5/02/2009, Jim Idle wrote:
>@after is not supported in the C target. Use this:
>
>statement
>@init { /* Empty */ }
>: ( x | Y | x | g)
> {
> sse.afterStatement();
> }
>;
Isn't that semantically different? I thought the point of @after
is that it's like "finally" code -- it gets executed regardless of
success/failure/explosions. Whereas an inline block at the end of
the rule would only get executed on a successful match.
(Although parser rules should usually not fail anyway, so it may
be a moot point.)
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
-~----------~----~----~----~------~----~------~--~---