Lines Matching refs:Recovery
70 # but no token is consumed during recovery...another error is found,
132 support code essentially; most of it is error recovery stuff and
182 # wack everything related to error recovery
200 single token insertion or deletion error recovery. If
204 recovery, override recoverFromMismatchedToken() and have it
252 # then we know we're missing a token; error recovery is free to
264 not parsing. Once in recovery mode, no errors are generated.
265 To get out of recovery mode, the parser must successfully match
269 2. enter recovery mode, report error
463 # where LT(1) is in the recovery token set so nothing is
478 A hook to listen in on the token consumption during error recovery.
487 A hook to listen in on the token consumption during error recovery.
496 Compute the error recovery set for the current rule. During
547 For error recovery, we cannot consider FOLLOW(c)
560 the same recovery set and doesn't consume anything. Rule b
565 for the token that was a member of the recovery set.
569 ANTLR's error recovery mechanism is based upon original ideas:
575 "A note on error recovery in recursive descent parsers":
580 "Efficient and Comfortable Error Recovery in Recursive Descent
761 """Conjure up a missing token during error recovery.
787 ## recovery. It handles "single token insertion" error recovery for
789 ## true if recovery was possible else return false.
825 error recovery.
1052 uses simplified match() and error recovery mechanisms in the interest
1270 ## TODO: not thought about recovery in lexer yet.
1337 to do sophisticated error recovery if you are in a fragment rule.
