| java.lang.Object org.antlr.tool.Message
All known Subclasses: org.antlr.tool.ToolMessage, org.antlr.tool.RecursionOverflowMessage, org.antlr.tool.LeftRecursionCyclesMessage, org.antlr.tool.GrammarDanglingStateMessage, org.antlr.tool.NonRegularDecisionMessage, org.antlr.tool.GrammarNonDeterminismMessage, org.antlr.tool.GrammarSyntaxMessage, org.antlr.tool.GrammarInsufficientPredicatesMessage, org.antlr.tool.GrammarUnreachableAltsMessage, org.antlr.tool.GrammarAnalysisAbortedMessage, org.antlr.tool.GrammarSemanticsMessage,
Message | abstract public class Message (Code) | | The ANTLR code calls methods on ErrorManager to report errors etc...
Rather than simply pass these arguments to the ANTLRErrorListener directly,
create an object that encapsulates everything. In this way, the error
listener interface does not have to change when I add a new kind of
error message. I don't want to break a GUI for example every time
I update the error system in ANTLR itself.
To get a printable error/warning message, call toString().
|
locationST | public StringTemplate locationST(Code) | | |
messageFormatST | public StringTemplate messageFormatST(Code) | | |
msgST | public StringTemplate msgST(Code) | | |
reportST | public StringTemplate reportST(Code) | | |
Message | public Message(int msgID)(Code) | | |
getLocationTemplate | public StringTemplate getLocationTemplate()(Code) | | Return a new template instance for the location part of a Message.
TODO: Is this really necessary? -Kay
|
getMessageTemplate | public StringTemplate getMessageTemplate()(Code) | | Return a new template instance every time someone tries to print
a Message.
|
setColumn | public void setColumn(int column)(Code) | | |
setLine | public void setLine(int line)(Code) | | |
setMessageID | public void setMessageID(int msgID)(Code) | | |
toString | public String toString(StringTemplate messageST)(Code) | | |
|
|