Page 1 of 7 Results 1 - 10 of 64

Errata Entries Order by:  Page Number  Reported By  Reported On  Fixed In Build
Pg: 68
Status: Fixed
Fixed in Build: 14
Reported On: 2019-01-10
Reported By:
Location: 3.3.3 - Assigning values to variables - primitive assignment
Old Text:
For example, you know that the size of a byte (8 bits) is smaller than the size of an int (16 bits)
New Text:
For example, you know that the size of a byte (8 bits) is smaller than the size of an int (32 bits)
Comments:

Pg: 103
Status: Fixed
Fixed in Build: 16
Reported On: 2019-02-07
Reported By: Username987654
Location: 4.3.1
Old Text:
iaa[0] = new int[2]; //ia[0] points to an array of ints of length 2 iaa[1] = new int[3]; //ia[1] points to an array of ints of length 3
New Text:
iaa[0] = new int[2]; //iaa[0] points to an array of ints of length 2 iaa[1] = new int[3]; //iaa[1] points to an array of ints of length 3
Comments:
ia should be iaa (in comments)
Pg: 104
Status: Fixed
Fixed in Build: 10
Reported On: 2018-12-02
Reported By: -
Location: 4.3.1 - multidimensional-arrays
Old Text:
You cannot, however, leave out the size of a higher dimension if you want to specify the size of a lower dimension. For example, you cannot do new int[][2]; This is not possible because the number of int[][] references depends on how many int[] objects do you have. If you have three int[] objects, that means you will have 3x2 = 6 int[][] references. The JVM cannot figure this out without knowing the length of all the higher dimensions.
New Text:
You cannot, however, leave out the size of a higher dimension if you want to specify the size of a lower dimension. For example, you cannot do new int[][2]; The reason is simple - new int[][2] tries to create an array of int[2] objects. But it it does not tell the JVM how many int[2] objects you want to store. Without this information, the JVM has no idea how much space it needs to allocate for this array. On the other hand, new int[2][] is fine because now, you are telling the JVM that you want to create an array of length 2. In this case, the JVM is clear that it needs to allocate space to store 2 references. Remember that the size of a reference doesn't depend on the length of the array to which it points. So, the JVM doesn't care about the length of the arrays to which these two references will refer. It simply allocates space to store 2 references.
Comments:

Pg: 292
Status: Fixed
Fixed in Build: 08
Reported On: 2018-11-20
Reported By: --
Location: 10.4 - Exceptions thrown by Application Programmer
Old Text:
$\vert$$\vert$
New Text:
||
Comments:
Mistake in typesetting of the paperback version. Kindle version is fine.
Pg: 182
Status: Fixed
Fixed in Build: 31
Reported On: 2020-06-04
Reported By: addy12345
Location: 8.1.2 - Returning values of different types from a method - Point 2 Autoboxing/Unboxing
Old Text:
Java allows a return value to be a reference to a wrapper class if the return type is of a primitive type of the same or smaller type. ... The reverse is also allowed:
New Text:
Java allows a return value to be a reference to a wrapper class if the return type is of a primitive type of the same or smaller type. ... The reverse is also allowed but only when the method's return type is a wrapper of the same type as the type of the primitive value being returned -
Comments:

Pg: 167
Status: Fixed
Fixed in Build: 29
Reported On: 2020-03-06
Reported By: ardurn
Location: 7.5.2 Syntax of the enhanced for loop
Old Text:
java.util.Iterable
New Text:
java.lang.Iterable
Comments:

Pg: 375
Status: Fixed
Fixed in Build: 29
Reported On: 2020-03-31
Reported By: ardurn
Location: 12.5.3 Last line of point 4
Old Text:
You could create a Predicate out of the equals method like this - Predicate equals = Predicate.isEquals(c1);.
New Text:
You could create a Predicate out of the equals method like this - Predicate equals = Predicate.isEqual(c1);
Comments:
It should be isEquals instead of isEquals.
Pg: 252
Status: Fixed
Fixed in Build: 29
Reported On: 2020-03-31
Reported By: ardurn
Location: 12.3.4 point 4
Old Text:
Using the isEquals method - ... isBefore/isAfter/isEquals
New Text:
Using the isEqual method - ... isBefore/isAfter/isEqual
Comments:

Pg: 272
Status: Fixed
Fixed in Build: 07
Reported On: 2018-10-17
Reported By: Arold Aroldson
Location: 10.2.0 - differentiate-among-checked-exceptions-unchecked-exceptions-and-errors
Old Text:
Diagram showing various exceptions shows ClassCastException under checked exceptions
New Text:
Diagram showing various exceptions shows ClassCastException under unchecked exceptions
Comments:
Associated text is correct. Only the diagram is incorrect.
Pg: 110
Status: Fixed
Fixed in Build: 06
Reported On: 2018-10-07
Reported By: Cristian Palau
Location: 5.1.1 - overview-of-operators-available-in-java
Old Text:
System.out.println(false != flag); //comparing a boolean with a Boolean, prints true because flag is false
New Text:
System.out.println(false != flag); //comparing a boolean with a Boolean, prints false because flag is false
Comments:

Page 1 of 7 Results 1 - 10 of 64