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 |
|---|---|---|---|---|---|
| PDF, ePub | Page 69 paragraph below the info box about the #tap method |
The name of the method must be #read_string, not #read_string? because it does not have a boolean return value. In the code sample a couple of lines above it is named correctly. Note from the Author or Editor: |
sebroeder | Jun 03, 2013 | |
Page 70 4th paragraph |
The accept states in the figure given are wrong. State 3 and state 5 are shown as accept states while they are not accept states. State 4 is not show as accept state while it actually is an accept state (the only one). Note from the Author or Editor: |
Michel Rijnders | May 21, 2013 | May 31, 2013 | |
Page 77 figure |
State 4 is an accept state, so the circle around the 4 should have a double-line border, not a single-line border. (See http://computationbook.com/errata/2.) |
Tom Stuart |
May 23, 2013 | May 31, 2013 | |
Page 259 Middle paragraph |
Accidentally repeated word: "to to" should be "to" in "Of course, this scheme of encoding a program as a large number is what makes it possible ***to to*** store it on disk,..." |
Jacob Quant | Aug 08, 2015 |