Public Member Functions | |
| def | __init__ |
| def | getCurrentInputSymbol |
| def | getMissingSymbol |
| def | getSourceName |
| def | getTokenStream |
| def | reset |
| def | setTokenStream |
| def | traceIn |
| def | traceOut |
Public Attributes | |
| input | |
Detailed Description
@brief Baseclass for generated parser classes.
Definition at line 1368 of file recognizers.py.
Constructor & Destructor Documentation
| def rve_interface_gen.antlr3.recognizers.Parser.__init__ | ( | self, | |
| lexer, | |||
state = None |
|||
| ) |
Reimplemented in rve_interface_gen.InterfaceParser.InterfaceParser.
Definition at line 1373 of file recognizers.py.
Member Function Documentation
| def rve_interface_gen.antlr3.recognizers.Parser.getCurrentInputSymbol | ( | self, | |
| input | |||
| ) |
Match needs to return the current input symbol, which gets put into the label for the associated token ref; e.g., x=ID. Token and tree parsers need to return different objects. Rather than test for input stream type or change the IntStream interface, I use a simple method to ask the recognizer to tell me what the current input symbol is. This is ignored for lexers.
Reimplemented from rve_interface_gen.antlr3.recognizers.BaseRecognizer.
Definition at line 1385 of file recognizers.py.
| def rve_interface_gen.antlr3.recognizers.Parser.getMissingSymbol | ( | self, | |
| input, | |||
| e, | |||
| expectedTokenType, | |||
| follow | |||
| ) |
Conjure up a missing token during error recovery.
The recognizer attempts to recover from single missing
symbols. But, actions might refer to that missing symbol.
For example, x=ID {f($x);}. The action clearly assumes
that there has been an identifier matched previously and that
$x points at that token. If that token is missing, but
the next token in the stream is what we want we assume that
this token is missing and we keep going. Because we
have to return some token to replace the missing token,
we have to conjure one up. This method gives the user control
over the tokens returned for missing tokens. Mostly,
you will want to create something special for identifier
tokens. For literals such as '{' and ',', the default
action in the parser or tree parser works. It simply creates
a CommonToken of the appropriate type. The text will be the token.
If you change what tokens must be created by the lexer,
override this method to create the appropriate tokens.
Reimplemented from rve_interface_gen.antlr3.recognizers.BaseRecognizer.
Definition at line 1389 of file recognizers.py.
Definition at line 1418 of file recognizers.py.
Definition at line 1414 of file recognizers.py.
reset the parser's state; subclasses must rewinds the input stream
Reimplemented from rve_interface_gen.antlr3.recognizers.BaseRecognizer.
Definition at line 1379 of file recognizers.py.
| def rve_interface_gen.antlr3.recognizers.Parser.setTokenStream | ( | self, | |
| input | |||
| ) |
Set the token stream and reset the parser
Definition at line 1406 of file recognizers.py.
| def rve_interface_gen.antlr3.recognizers.Parser.traceIn | ( | self, | |
| ruleName, | |||
| ruleIndex | |||
| ) |
Definition at line 1422 of file recognizers.py.
| def rve_interface_gen.antlr3.recognizers.Parser.traceOut | ( | self, | |
| ruleName, | |||
| ruleIndex | |||
| ) |
Definition at line 1426 of file recognizers.py.
Member Data Documentation
Reimplemented from rve_interface_gen.antlr3.recognizers.BaseRecognizer.
Definition at line 1406 of file recognizers.py.
The documentation for this class was generated from the following file: