Lines Matching full:rule
59 # Track the set of token types that can follow any rule invocation.
80 # the stop token index for each rule. ruleMemo[ruleIndex] is
82 # get back the stop token for associated rule or MEMO_RULE_FAILED.
84 # This is only used if rule memoization is on (which it is by default).
98 # matching lexer rule(s). If you subclass to allow multiple token
206 This way any error in a rule will cause an exception and
207 immediate exit from rule. Rule would recover by resynchronizing
208 to the set of symbols that can follow rule ref.
389 msg = "rule " \
496 Compute the error recovery set for the current rule. During
497 rule invocation, the parser pushes the set of tokens that can
498 follow that rule reference on the stack; this amounts to
499 computing FIRST of what follows the rule reference in the
500 enclosing rule. This local follow set only includes tokens
501 from within the rule; i.e., the FIRST computation done by
502 ANTLR stops at the end of a rule.
507 consistent with any of the alternatives for rule r. The best
509 can legally follow a call to r *or* any rule that called r.
524 At each rule invocation, the set of tokens that could follow
525 that rule is pushed on a stack. Here are the various "local"
538 depth local follow set after call to rule
544 been called from a different context in rule a for ')' to be
555 not consume anything and after printing an error rule c would
559 set). The rule exception handler tries to recover, but finds
560 the same recovery set and doesn't consume anything. Rule b
561 exits normally returning to rule a. Now it finds the ']' (and
593 Compute the context-sensitive FOLLOW set for current rule.
594 This is set of token types that can follow a specific rule
598 definition of plain FOLLOW for rule r:
621 FOLLOW sets are precisely what could follow a rule reference.
654 # can we see end of rule?
656 # Only leave EOR in set if at top (start rule); this lets
657 # us know if have to include follow(start rule); i.e., EOF
662 # can't see end of rule, quit
696 reference in rule atom. It can assume that you forgot the ')'.
822 in the parser java code a rule is invoked.
845 pass in, for example, a RecognitionException to get it's rule
913 Given a rule number and a start token index number, return
914 MEMO_RULE_UNKNOWN if the rule has not parsed input starting from
915 start index. If this rule has parsed input starting from the
916 start index before, then return where the rule stopped parsing.
917 It returns the index of the last token matched by the rule.
930 Has this rule already parsed input at the current index in the
936 this rule and successfully parsed before, then seek ahead to
937 1 past the stop token matched for this rule last time.
955 Record whether or not this rule parsed the input at this position
1132 Instruct the lexer to skip creating a token for current lexer rule
1134 a lexer rule finishes with token set to SKIP_TOKEN. Recall that
1135 if token==null at end of any token rule, it creates one for you
1163 outermost lexical rule. The token object should point into the
1336 it all works out. You can instead use the rule invocation stack
1337 to do sophisticated error recovery if you are in a fragment rule.
1462 to get the .text property anyway if the rule matches tokens from multiple
