Edmund Yong wrote:Page 385: The last line should read "Since String does NOT implement Canine,...".
Edmund Yong wrote:Page 409: In table 10.1, for Error type, it is "No" for the question "Okay for program to catch?". Shouldn't this be "Yes" instead? It may be bad practice to catch an Error, but the compiler is not going to complain if you try to catch an Error. After all, an Error is an unchecked exception, and it's okay to catch an unchecked exception. This is demonstrated on page 448 question 22, in which StackoverflowError is a valid type to catch.
Edmund Yong wrote:Page 445: For question 12, isn't F a correct answer as well since an uncaught NumberFormatException is thrown?
[OCP 21 book] | [OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Jeanne Boyarsky wrote:
Edmund Yong wrote:Page 445: For question 12, isn't F a correct answer as well since an uncaught NumberFormatException is thrown?
No. This is a single answer question (note there is not a "choose all that apply"). Option A includes the output and the NumberFormatException. Option F just addresses the exception. Remember that an unhandled exception does result in a stack trace.
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)
RTFJD (the JavaDocs are your friends!) If you haven't read them in a long time, then RRTFJD (they might have changed!)