Java Pocket Guide

Errata for Java Pocket Guide

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page Safari
Safari

There is a typo in the book by link: https://www.safaribooksonline.com/library/view/java-pocket-guide/9781491938683/ch04.html Class Song { String title; Artist artist; float length; Year year; void setData() {...} } Word "class" should not starts with capital letter here.

Note from the Author or Editor:
I agree. 'Class' should read 'class'. Thank you for the errata submission. Robert

Anonymous  Oct 17, 2017  Nov 10, 2017
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 224
Middle of page

The optional static modifier of the requires keyword is not listed. This feature is not documented in the chapter either.

Note from the Author or Editor:
On page 224, please change: [requires [transitive] <module name>] should read [requires [transitive] [static] <module name>] On page 225, please add this sentence to the end of the Declaring Dependencies section. The optional static keyword is for compile time dependencies.

Matthew Halverson  Oct 07, 2017  Nov 10, 2017
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 224
Middle of page

The syntax for the opens and exports statements allow multiple comma separated qualified module names and the provides statement allows multiple types to be listed. The text strongly suggest that only one package/type is allowed.

Note from the Author or Editor:
On page 224, please change this statement: "All public types in a package may be exported by adding an export statement to a module definition:" to the following: "All public types in a package may be exported by adding one or more export statements to the module definition:"

Matthew Halverson  Oct 07, 2017  Nov 10, 2017