Page 6 of 7 Results 51 - 60 of 64

Errata Entries Order by:  Page Number  Reported By  Reported On  Fixed In Build
Pg: 242
Status: Fixed
Fixed in Build: 14
Reported On: 2019-01-07
Reported By: Username987654
Location: 9.3.2 - Valid combinations of access modifiers, abstract, final, and static
Old Text:
class Sofa
New Text:
abstract class Sofa
Comments:
Although not relevant for this discussion, the Cclass shown under "Impact of access modifiers on abstract and final" should be abstract.
Pg: 82
Status: Fixed
Fixed in Build: 14
Reported On: 2019-01-09
Reported By: OCAJO1
Location: 3.5.3 - Garbage Collection for the exam
Old Text:
Diagrams are off by 1 step. Diagrams shown at step 2, 3, 4 should be at step 1, 2, and 3.
New Text:
Diagrams are aligned with the steps
Comments:
Diagrams and steps are correct. Only their alignment is wrong.
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: 237
Status: Fixed
Fixed in Build: 12
Reported On: 2019-01-04
Reported By: Username987654
Location: 9.1.5 Benefits of Inheritance
Old Text:
For example, in the class hierarchy consisting of the CurrentAccount, SavingsAccount, and RetirementAccount classes...
New Text:
For example, in the class hierarchy consisting of the Account, CheckingAccount, and SavingsAccount classes...
Comments:

Pg: 235
Status: Fixed
Fixed in Build: 12
Reported On: 2019-01-04
Reported By: Username987654
Location: 9.1.3 Inheritance and access modifiers - point 5
Old Text:
Even though the balance field of Account is visible and inherited in RetirementAccount, acct.balance ...
New Text:
Even though the balance field of Account is visible and inherited in RetirementAccount, sa.balance ...
Comments:
acct.balance should be changed to sa.balance
Pg: 208
Status: Fixed
Fixed in Build: 12
Reported On: 2019-01-03
Reported By: Username987654
Location: 8.5.2 Creating constructors
Old Text:
this.someValue = x; //initializing x
New Text:
this.someValue = x; //initializing someValue
Comments:

Pg: 51
Status: Fixed
Fixed in Build: 12
Reported On: 2019-01-02
Reported By: OCAJO1
Location: 2.7 Compare and contrast the features and components of Java - Point 6
Old Text:
A Java application can be run with a .
New Text:
A Java application can be run with a Security Manager.
Comments:

Pg: 103
Status: Fixed
Fixed in Build: 10
Reported On: 2018-12-02
Reported By: Username987654
Location: 4.3.1 - multidimensional-arrays
Old Text:
Example 1 has [2][3], while here, it is [2][]...[2] implies that you want to store two references. In other of words, the length of your array (which is of type array of ints) is 2.
New Text:
Example 1 has [2][3], while here, it is [3][]...[3] implies that you want to store three references. In other of words, the length of your array (which is of type array of ints) is 3.
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: 71
Status: Fixed
Fixed in Build: 09
Reported On: 2018-11-26
Reported By: Username987654
Location: 3.3.3 - Assigning float to int or double to long and vice-versa
Old Text:
Two errors - 1. Part of the sentence, "Java allows such assignments without a cast because it is possible to get back the exact same int or long value from a float or a double if you round them off." must be removed. 2. The statement, "i = f1; //will not compile" in the code should be removed.
New Text:
Java allows such assignments without a cast nonetheless.
Comments:

Page 6 of 7 Results 51 - 60 of 64