Lines Matching refs:exception
205 throw an exception. See TreeParser.recoverFromMismatchedToken().
206 This way any error in a rule will cause an exception and
299 exception types?
303 exception classes. This also makes it much easier for the exception
304 handling because the exception classes do not have to have pointers back
306 the message for an exception type would be difficult because you
307 would have to subclassing exception, but then somehow get ANTLR
308 to make those kinds of exception objects instead of the default.
318 exception types.
506 When you find a "no viable alt exception", the input is not
558 exception (since LA(1) is not in the viable following token
559 set). The rule exception handler tries to recover, but finds
643 throwing an exception.
682 exception For example, Input 'i=(3;' is clearly missing the
709 # report after consuming so AW sees the token in the exception
724 # report after inserting so AW sees the token in the exception
728 # even that didn't work; must throw the exception
796 ## # nothing to do; throw exception
1004 throw an exception not under RecognitionException and Java will naturally
1006 lexing then you should not throw an exception to the parser--it has already
