schrodinger.application.desmond.antlr3.exceptions module¶
ANTLR3 exception hierarchy
- exception schrodinger.application.desmond.antlr3.exceptions.BacktrackingFailed¶
Bases:
Exception
@brief Raised to signal failed backtrack attempt
- exception schrodinger.application.desmond.antlr3.exceptions.RecognitionException(input=None)¶
Bases:
Exception
@brief The root of the ANTLR exception hierarchy.
To avoid English-only error messages and to generally make things as flexible as possible, these exceptions are not created with strings, but rather the information necessary to generate an error. Then the various reporting methods in Parser and Lexer can be overridden to generate a localized error message. For example, MismatchedToken exceptions are built with the expected token type. So, don’t expect getMessage() to return anything.
Note that as of Java 1.4, you can access the stack trace, which means that you can compute the complete trace of rules from the start symbol. This gives you considerable context information with which to generate useful error messages.
ANTLR generates code that throws exceptions upon recognition error and also generates code to catch these exceptions in each rule. If you want to quit upon first error, you can turn off the automatic error handling mechanism using rulecatch action, but you still need to override methods mismatch and recoverFromMismatchSet.
In general, the recognition exceptions can track where in a grammar a problem occurred and/or what was the expected input. While the parser knows its state (such as current input symbol and line info) that state can change before the exception is reported so current token index is computed and stored at exception time. From this info, you can perhaps print an entire line of input not just a single token, for example. Better to just say the recognizer had a problem and then let the parser figure out a fancy report.
- __init__(input=None)¶
- extractInformationFromTreeNodeStream(nodes)¶
- getUnexpectedType()¶
Return the token type or char of the unexpected input element
- property unexpectedType¶
Return the token type or char of the unexpected input element
- exception schrodinger.application.desmond.antlr3.exceptions.MismatchedTokenException(expecting, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.RecognitionException
@brief A mismatched char or Token or tree node.
- __init__(expecting, input)¶
- exception schrodinger.application.desmond.antlr3.exceptions.UnwantedTokenException(expecting, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.MismatchedTokenException
An extra token while parsing a TokenStream
- getUnexpectedToken()¶
- exception schrodinger.application.desmond.antlr3.exceptions.MissingTokenException(expecting, input, inserted)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.MismatchedTokenException
We were expecting a token but it’s not found. The current token is actually what we wanted next.
- __init__(expecting, input, inserted)¶
- getMissingType()¶
- exception schrodinger.application.desmond.antlr3.exceptions.MismatchedRangeException(a, b, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.RecognitionException
@brief The next token does not match a range of expected types.
- __init__(a, b, input)¶
- exception schrodinger.application.desmond.antlr3.exceptions.MismatchedSetException(expecting, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.RecognitionException
@brief The next token does not match a set of expected types.
- __init__(expecting, input)¶
- exception schrodinger.application.desmond.antlr3.exceptions.MismatchedNotSetException(expecting, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.MismatchedSetException
@brief Used for remote debugger deserialization
- exception schrodinger.application.desmond.antlr3.exceptions.NoViableAltException(grammarDecisionDescription, decisionNumber, stateNumber, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.RecognitionException
@brief Unable to decide which alternative to choose.
- __init__(grammarDecisionDescription, decisionNumber, stateNumber, input)¶
- exception schrodinger.application.desmond.antlr3.exceptions.EarlyExitException(decisionNumber, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.RecognitionException
@brief The recognizer did not match anything for a (..)+ loop.
- __init__(decisionNumber, input)¶
- exception schrodinger.application.desmond.antlr3.exceptions.FailedPredicateException(input, ruleName, predicateText)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.RecognitionException
@brief A semantic predicate failed during validation.
Validation of predicates occurs when normally parsing the alternative just like matching a token. Disambiguating predicate evaluation occurs when we hoist a predicate into a prediction decision.
- __init__(input, ruleName, predicateText)¶
- exception schrodinger.application.desmond.antlr3.exceptions.MismatchedTreeNodeException(expecting, input)¶
Bases:
schrodinger.application.desmond.antlr3.exceptions.RecognitionException
@brief The next tree mode does not match the expected type.
- __init__(expecting, input)¶