Errata for The Definitive ANTLR Reference

#29899: middle of page: You could say that the file has no structure or that the structure is simply “one or more characters.”

Should be “zero or more characters.”

The comment in the code block of the following page is correct.--Manfred Bartz

#29978: In the upper half of the page, a source code sample is given. There is stated that a grammer such as:

multExpr returns [int value]

will lead to the Java Code:

public int expr() throws ...

I assume this should be:

public int multExpr() throws ...
--Thomas

#29405: After the testing the expression recognizer, the text says "ANTLR doesn't emit any output because there are no actions and grammar". There is definitely a grammar... this must mean "there are no actions in the grammar.--A Rooks

#29384: In the Literals section, the "one-character string containing the single quote character" is missing the closing single quote. I.e. it is shown as '\" instead of '\"'--Dan S.

#29382: "Lexer rules can force the lexer to emit more token" should be "Lexer rules can force the lexer to emit more than one token". Also, you probably should move the sentence that comes before the "Emitting More Than One Token per Lexer Rule" down after the header.--Andy Tripp

#29412: "There are two tokens in this case:" is followed by a list of three tokens with types 4, 5, and 6. One is a literal '+', but isn't that still a token?--A Rooks

#29413: The first sentence about the ASTLabelType option contains "all node variables pointers", which doesn't look right. Shouldn't it be "all node variable pointers"? Or maybe it's intended to be possessive: "all node variables' pointers".--A Rooks

#31561: In the generated code for a(), the "System.out.println("exiting");" line should actually be "System.out.println("after matching rule; before finally");" per the definition of @after on the preceeding page.--Dan Delorey

#32415: This is a minor point, but in the paragraph discussing $ruleRef, I think the references to "$rulename" and "rulename" should be updated to "$ruleRef" instead, for consistency.--I. Firkusny

#29381: On page 181 of the PDF and page 168 of the dead-tree version, we have:

variableDefinition
: modifiers type ID ('=' expression)? ';'
-> {inMethod}? ^(VARIABLE ID modifier* type expression?)
-> ^(FIELD ID modifier* type expression?)
;

...where "modifiers" should be changed to "modifier*" (or vice-versa).
--Andy Tripp

#29423: The first paragraph of Chap 9 contains "from an internal data structures". The cardinalities are mismatched :-) It should say "an internal data structure" or "internal data structures".--A Rooks

#29459: The lead-in to the example says "override two methods from BaseRecognizer, displayRecognitionError( ) and getTokenErrorDisplay( )". However, it looks like getErrorMessage( ) and getTokenErrorDisplay( ) are overridden in the example. Should "displayRecognitionError" be changed to "getErrorMessage" in the lead-in?--A Rooks

#29532: The paragraph beginning "The beauty of this solution is that a syntactic predicates handles ..." contains a typo. It should say "a syntactic predicate" (singular) OR remove "a" and change "handles" to "handle".--A Rooks

#32438: In the anecdote box at the top of the page:

"""
“That ’;’ came as a complete surprise to me at this point your program.”
"""

Should be "this point OF your program".--Vaclav Slavik