App Engine Python SDK  v1.6.9 rev.445
The Python runtime is available as an experimental Preview feature.
Public Member Functions | Public Attributes | Properties | List of all members
google.appengine._internal.antlr3.exceptions.RecognitionException Class Reference
Inheritance diagram for google.appengine._internal.antlr3.exceptions.RecognitionException:
google.appengine._internal.antlr3.exceptions.EarlyExitException google.appengine._internal.antlr3.exceptions.FailedPredicateException google.appengine._internal.antlr3.exceptions.MismatchedRangeException google.appengine._internal.antlr3.exceptions.MismatchedSetException google.appengine._internal.antlr3.exceptions.MismatchedTokenException google.appengine._internal.antlr3.exceptions.MismatchedTreeNodeException google.appengine._internal.antlr3.exceptions.NoViableAltException google.appengine._internal.antlr3.exceptions.MismatchedNotSetException google.appengine._internal.antlr3.exceptions.MissingTokenException google.appengine._internal.antlr3.exceptions.UnwantedTokenException

Public Member Functions

def __init__
 
def extractInformationFromTreeNodeStream
 
def getUnexpectedType
 

Public Attributes

 node
 
 token
 
 line
 
 charPositionInLine
 
 approximateLineInfo
 

Properties

 unexpectedType = property(getUnexpectedType)
 

Detailed Description

@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.

Member Function Documentation

def google.appengine._internal.antlr3.exceptions.RecognitionException.getUnexpectedType (   self)
Return the token type or char of the unexpected input element

The documentation for this class was generated from the following file: