The latest version of the book is P2.0, released 18 days ago. If you've bought a PDF of the book and would like to update it to this version (for free), visit your home page.
By default this page displays the errata for the latest version of the book. If you have a previous version, select it here:
If you've found a new error, please submit it.
- Reported in: P2.0 (11-Nov-19)
PDF page: 315
2 typo i think:
in page 315
1 ovicide, 187
there is no "ovicide" in page 187
in page 316
Program Evaluation Review
Technique, see PERT"The ii tag should not be here."
in the index, there is one for "Program Evaluation Review
Technique, see PERT" which followed by a sentence "The ii tag should not be here."
i think the second line is a mistake.
- Reported in: P2.0 (13-Nov-19)
Paper page: 134
"Don't chain method calls" tip should really be expanded out more or be removed. With the revitalization of functional programming, chaining becomes common practice. I assumed the issue before would have been over null pointers, but nulls are blasphemous in FP style coding. Focusing the topic on applications volatility is a red herring for a reason not to chain. Type-safe languages will easily pick up issues at compile time.--Jeffrey
- Reported in: P1.0 (13-Nov-19)
Paper page: 151
PG 151, Footnote 5, typo in name of the language
... Isobelle/ML ... ->
... Isabelle/ML ...--William Denman
- Reported in: P2.0 (30-Oct-19)
PDF page: 238
in Note 18
"If you’re seeing this in black and white and want the color version, or if you’re having trouble distinguishing colors and want to try the grayscale version, pop over to ...."
and i think the version in the book is grayscale version??? is it?--RBK