Errata
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 |
---|---|---|---|---|---|
ePub | Page 4 Just before "Defining the Problem" |
Needless space before apostrophe Note from the Author or Editor: |
Eric Willigers | Sep 13, 2014 | |
Page 16 2nd paragraph |
Examples include the amount of memory is your node using Note from the Author or Editor: |
Eric Willigers | Sep 16, 2014 | ||
Page 19 last paragraph |
the call fails as none of the clauses matches. Note from the Author or Editor: |
Eric Willigers | Sep 16, 2014 | ||
Printed, PDF, ePub, Mobi, , Other Digital Version | Page 39 2nd paragraph |
the record definition 'hostent' is missing commas between the fields Note from the Author or Editor: |
the rac | Jun 21, 2016 | |
Page 105 Full sweep of the heap |
but x you should pick your own Note from the Author or Editor: |
Eric Willigers | Sep 17, 2014 | ||
ePub | Page 113 First sentence |
"If want to let the supervisor continue to start workers� Note from the Author or Editor: |
Derek Brown | Jun 24, 2014 | |
Page 116 Second Paragraph |
In the sentence Note from the Author or Editor: |
mjtlx | Mar 15, 2016 | ||
Page 124 last paragraph |
a asynchronous --> an asynchronous Note from the Author or Editor: |
Shayan Pooya | Jun 09, 2014 | ||
Page 137 Bottom code listing |
stop() calls gen_fsm:sync_send_all_state_event, but we implement handle_event (not handle_sync_event). Maybe stop() should call gen_fsm:send_all_state_event instead? Note from the Author or Editor: |
John Gallagher | Mar 17, 2016 | ||
Page 154 Sample run in the middle |
`terminate/3` function at the top of page 154 doesn't contain any code to display: Note from the Author or Editor: |
Yuce Tekol | Dec 25, 2015 | ||
ePub | Page 161 First sentence of first paragraph |
"So, what's is happening?" Note from the Author or Editor: |
Derek Brown | Dec 18, 2014 | |
Printed, PDF, ePub | Page 191 last paragraph |
The text says "Keep in mind that terminate_child/2, restart_child/2, and delete_child/2 cannot be used with simple_one_for_one strategies:" but this is not completely correct. The terminate_child/2 function can be used with simple_one_for_one as long as the child process pid, not the child specification identifier, is passed for the second argument. This is clearly documented under http://erlang.org/doc/man/supervisor.html#terminate_child-2 : "If the supervisor is simple_one_for_one, Id must be the pid() of the child process." |
Steve Vinoski |
Jul 19, 2016 | |
Printed, PDF, ePub | Page 199 Before "Abnormal or Normal Termination?" section |
In the last sentence above the mentioned section is written: "How to you test these scenarios and detect these design anomalies?" Note from the Author or Editor: |
Carlos Galdino | Jul 03, 2016 | |
Page 239 Last paragraph |
Typo: "netspilt" Note from the Author or Editor: |
Yuce Tekol | Dec 26, 2015 | ||
Page 372 2nd paragraph |
Duplicated sentence: |
Johan Wärlander | Nov 03, 2015 |