Errata

System.getProperty("user.dir")); // e.g., /users/pat"

the second ')' should be omitted, and the example should be like this

"System.getProperty("user.dir"); // e.g., /users/pat"

"This ATTLIST says that the Animal element has a class attribute that can have" should read "This ATTLIST says that the Animal element has a animalClass attribute that can have"

"we first create the WEB/INF and WEB-INF/classes directories" should read "we first create the WEB-INF and WEB-INF/classes directories"

Note from the Author or Editor:
Thanks!

The line of code:

float length = 10.0;

is flagged as a type mismatch error by the Java compiler. The 'F' suffix is missing from the declaration of the floating-point constant. The line of code should be:

float length = 10.0F;

Note from the Author or Editor:
thanks!

The text says, "In general, a good implementation can operate in linear time for putting and retrieving elements." Linear time for a hash would be horrible performance. It should read, "In general, a good implementation can operate in constant time for putting and retrieving elements." The diagram below it does illustrate an algorithm (hash plus linked list) that is O(N) with a low constant. However, other algorithms are O(logN) and constant. I admit, I don't know what algorithm Java uses.

The C++ STL has a Map that performs in O(logN) time and a less official "hashed associative containers" that work in constant time. I assume Java would use similar technology.

calendard.setTime( now )
should read
calendar.setTime( now )

"frame.add" should be "frame.getContentPane().add"

"frame.add" should be "frame.getContentPane().add"

"frame.add" should be changed to "frame.getContentPane().add"

A credit card number consists of 16 digits, so the creditCardNumber[16] array has room for only the data and is not a null-terminated string. The %s format requires a null-terminated array.

To fix, change the printf line to
printf("Card number = %.16s\n", cardno);

Note from the Author or Editor:
I see it on page 15 of the printed edition, but yes he is correct. Please adjust to the text he shows above.

in the code example, the first line reads

Import java.io.*;

and should read

import java.io.*;

Note from the Author or Editor:
He is correct. "Import" should be all lower case.

The book states:

\b\w{5,7}\b // match words with at least 5 and at most 7 letters

However it should read "at least 5 and at most 7 characters" since \w would match digits and underscore characters as well as letters.

Note from the Author or Editor:
ok, let's change "letters" to "characters"

The book states:

For example, the following pattern matches a multiple-digit number with leading zeros:
0*\d+ // match a number (one or more digits) with leading zeros

However I think that it should state:

For example, the following pattern matches a number with one or more digits, plus optional leading zeros.
0*\d+ // match a number (one or more digits) with optional leading zeros

Note from the Author or Editor:
let's use his suggested wording.

Preceding code snippet on page 696:

g2.translate(50, 0);
g2.rotate(Math.PI / 6);

1st sentence currently reads:
"... (a shift of 50 units right and a rotation of 30 degrees counterclockwise)."

1st sentence should read:
"... (a shift of 50 units right and a rotation of 30 degrees clockwise)."

Note from the Author or Editor:
He is correct. Not sure how that slipped through all this time.

In the for loop header "collection" should be "col".

Note from the Author or Editor:
Confirmed, please change:

for( Date date : collection )

to:

for( Date date : col )

This line:

object[0] = new Date(); // Runtime ArrayStoreException!

Should read:

objects[0] = new Date(); // Runtime ArrayStoreException!

Note from the Author or Editor:
confirmed, please change.
it's on p 182 of the online edition, not sure where in print.

Is:
The second value (60) is a convention used to support leap years.

Should be:
The second value (60) is a convention used to support leap seconds.



For confirmation, go to:
iers.org
Search the web site for leap seconds,
Follow the IERS Glossary: Leap Seconds link
Click on the related link for Leap Seconds
And click on "here" in the "historical list of leap seconds can be found here" which will take you to
http://maia.usno.navy.mil/ser7/tai-utc.dat
The historical list shows many leap seconds (including eight of the last ten) that did not occur during Leap Years.

Note from the Author or Editor:
confirmed. Please change "leap years" to "leap seconds"

HelloComonent hello = new HelloComponent();
frame.add( hello );
->
frame.add( new HelloComponent() );

#########################################

frame.add( new HelloComponent2("Hello, Java!") );

should be:

frame.getContentPane().add( new HelloComponent2("Hello, Java!") );

(The equivalent line is correct on page 42)

Likewise

HelloComponent2 newObject = new HelloComponent2("Hello, Java!");
frame.add( newObject );

should be:

HelloComponent2 newObject = new HelloComponent2("Hello, Java!");
frame.getContentPane().add( newObject );

(probably worth checking for s/frame.add/frame.getContentPane().add/g thoughout)

Note from the Author or Editor:
I searched the current Safari version and found six instances of "frame.add". They should all be "frame.getContentPane().add" (five in chapter 2 and one in chapter 17)

Please let me know if this isn't specific enough.

Type double (64-bit, IEEE 754) was previously missing.
This entry HAS BEEN ADDED to the table.

prints the numbers 0 through 100
->
prints the numbers 0 through 99

#########################################

The number 1 is not a prime. At least according to all the number theory books I
have read.

Note from the Author or Editor:
Ok, change:

int [ ] primes = { 1, 2, 3, 5, 7, 7+4 }; // e. g. , primes[ 2] = 3

to:

int [ ] primes = { 2, 3, 5, 7, 7+4 }; // e. g. , primes[2] = 5

The last sentence in the paragraph says "In either case, if you don't initialize a
variable when you declare it, it's given a default value appropriate for its type
(null, zero, or false)."

"zero" is typeset in constant width font. According to the book preface, in the
"Conventions Used in This Book" section, constant width is for:
- anything that might appear in a Java program
- tags in HTML or XML
- keywords, objects and environment variables

I don't believe the author's intent is to say there is a Java keyword "zero", or a
constant named "zero", or an object with the name "zero", etc., which some variables
are initialized to. Instead, I believe they just mean the numeric value zero: "0".

Consider changing "zero" to "0", or eliminating the constant width font and using
regular font for "zero", so as to avoid implying that the string "zero" has special
significance in Java code.

Note from the Author or Editor:
He is correct. Please use the regular body text font for the zero in:

given a default value appropriate for its type (null, zero, or false).

The text explains an enum's compareTo() method as returning an integer greater
than zero when the target enum is greater than the reference enum (in the enum ordering).

Then the authors present the code snippet:

Level level = Level.HIGH;
Level anotherLevel = Level.LOW;
if (level.compareTo( anotherLevel ) > 0 ) // true
doSomething();

The "true" comment would lead one to believe that compareTo() returns an integer
greater than zero in this case. Since anotherLevel is the target enum, and level
is the reference enum, this implies that Level.LOW is greater than Level.HIGH
in the enum order.

It seems odd that LOW would be higher than HIGH, until one realizes that this
condition could be true, given the (counter-intuitive) enum order: { HIGH, ..., LOW }.
But since we aren't told in the example what the actual enum order is, it's not
possible to determine whether the "// true" comment is in fact accurate.

It would be helpful in this case to either include the enum declaration, provide
more detail in the text, or perhaps switch the places of the Level.HIGH and Level.LOW
tokens in the code.

Note from the Author or Editor:
Please swap the LOW and HIGH to:

Level level = Level.LOW;
Level anotherLevel = Level.HIGH;

The text reads:

"The java.io.Serializeable interface is a good example. Classes that implement
Serialize don't have to add any methods or variables."

The problem is the text first calls this interface Serializeable, but then calls
it Serialize. The correct name is Serializeable.

Note from the Author or Editor:
Correct: Please change: "Classes that implement
Serialize don't have to add any methods or variables"

To:

"Classes that implement
Serializeable don't have to add any methods or variables"

Rectangle2d.Float rect = new Rectangle2D.Float();
->
Rectangle2D.Float rect = new Rectangle2D.Float();

#########################################

In the last code example, in the try block, the code should read
"new ExceptionTester<ClassNotFoundException>().test(new ClassNotFoundException());"
rather than
"new E<ClassNotFoundException>().test(new ClassNotFoundException());".

Note from the Author or Editor:
Please change:

new E<ClassNotFoundException>().test(

to:

new ExceptionTester<ClassNotFoundException>().test(

The line
WorkRequest request , WorkListener listener)
should read
final WorkRequest request , final WorkListener listener)

The example code given on this site is correct, but the book leaves out both instances of the word "final".

Note from the Author or Editor:
please change:

public void asyncExecute(
WorkRequest request , WorkListener listener )

to:

public void asyncExecute(
final WorkRequest request, final WorkListener listener )

parser.parse( myfile.xml" );
->
parser.parse( "myfile.xml" );

#########################################