Hi Stefan Feenstra,
First of all, a warm welcome to CodeRanch!
Stefan Feenstra wrote:I am creating this topic because I noticed some content in the book which might not be fully true (But I might be mistaken, hence posting it in a seperate topic and not in the stickied thread).
Thanks for taking the time to create a new topic about your concerns/doubts about possible errata in the study guide. The authors will really appreciate it!

Please note that the stickied thread is about the errata of a different study guide (K&B7) covering OCA7 and OCP7. So posting it in a seperate topic was definitely the right thing to do
Stefan Feenstra wrote:Page 30The error shown on page 30 shows the error being on line 5
You are correct! This minor issue was
already reported and is already added to the
official errata overview (maintained by the authors).
Stefan Feenstra wrote:Page 34
Bit of a minor detail, perhaps out of the scope of the book.
However the book states that Class variables are in scope from declaration till the program ends. However classes can be GC'ed in java given that there are no references to the given class loader.
That is indeed waaay beyond the scope of the study guide.
Stefan Feenstra wrote:Page 36
My question is why doesn't this say anything about weak/soft references?
That is again way beyond the scope of the study guide. I believe it is even not in the scope of the OCPJP study guide.
Stefan Feenstra wrote:Page 40, possibly also in previous pages
Numerical literals according to the Oracle page includes floating point numbers (Since the example includes a float name = ...).
A minor detail/pitfall is that while a 0 prefix for a integer number (so without a decimal dot) becomes octal, the same does not go for constants that are interpreted as floating point numbers.
You are correct! And this edge case might be covered in the next version of the study guide. Very similar: if you use the suffix D or F with hexadecimal notation, it is considered as part of the literal and not the suffix for
double or
float. An illustrative code snippet of this behavior can be found
here.
Hope it helps!
Kind regards,
Roel
PS. Have a
cow for creating a very nice topic which comprises all your concerns/doubts about possible errata in one specific chapter. That makes it really very convenient for the authors to handle them. Also providing an illustrative code snippet is great!