Errata for The Definitive ANTLR 4 Reference

#50953: After creating the Hello.g4 sample grammar, then generating and compiling the Java, running grun leads to an error on Windows: "Can't load Hello as lexer or parser"

In addition, running grun with no parameters, does more than what you say in the book: It prints the usage messages and a NullPointerException stack trace

TestRig.main ->
TestRig.process ->
java.lang.ClassLoader.loadClass ->
sun.misc.Launcher.$AppClassLoader.loadClass

Here are the files in the local directory:

Hello.g4
Hello.tokens
HelloBaseListener.class
HelloBaseListener.java
HelloLexer.class
HelloLexer.java
HelloLexer.tokens
HelloListener.class
HelloListener.java
HelloParser$RContext.class
HelloParser.class
HelloParser.java

Here is the Hello.g4 file:

grammar hello; // define a grammar called Hello
r : 'hello' ID; // match keyword 'hello' followed by an identifier
ID : [a-z]+; // match lower-case identifiers
WS : [ \t\r\n]+ -> skip ; //skip spaces, tables, newlines, \r (Windows)

I'm running on Windows 7 Ultimate x86, 4GB RAM, 8 cores. --ALB

#50920: Running Translate on {99, 3, 451} as shown in the book works slick. But try {{1}} and Translate blows up with a NullPointerException in ShortToUnicodeString.enterValue. I'm guessing this is because the value in this case is not an integer but is a sublist {1}.--Roger House

#51004: Number in JSON.g4 grammar is defined wrongly. First alternative is wrong.

It doesn't accept floating point numbers that contain zero after period char. For e.g. number: 1.01 would be parsed as two number tokens: 1.0 and 1.

It's very easy to verify this running grun JSON value -tokens.--K.M.

#50786: The first clause for NUMBER in the JSON grammar seems to have an error because it does not allow a zero directly after the point as in the following number
1.05e+2
I tested it with this object:
{"name":"Gerhard", "age":51, "weight":1.05e+2}

--Gerhard Zorn

#50990: The text discusses the class PropertyFileBaseListener but instead of presenting the code for PropertyFileBaseListener, the code of the class PropertyFileBaseVisitor is presented.--Karl Stroetmann

#51162: Section 13.7 ("Maximizing Parser Speed") in the new ANTLR version 4 book says to use the code

parser.getInterpreter().setSLL(true);

to use the SLL parsing strategy, but there seems to be no such method on the class returned by parser.getInterpreter().

What seems to work instead is the following:

parser.getInterpreter().setPredictionMode( PredictionMode.SLL );--from list (via Terence Parr)