Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date submitted |
---|---|---|---|---|
Other Digital Version | 2.19 2.19 Perl solution |
The Perl replacement text appears as |
Gregory Sherman | Feb 25, 2018 |
Page 26 Solution, line 2 |
Ruby 1.9 regular expression editor (rubular.com) shows the following error in this code: Forward slashes must be escaped |
Anonymous | Mar 09, 2012 | |
Page 32 Shorthands, paragraph 3 |
Current text: |
Anonymous | Mar 09, 2012 | |
Page 65 Last sentence |
The last paragraph says "For variable repetition, we use the quantifier <{n,m}>, where n is a POSITIVE NUMBER and m in greater than n....". I think this should read "where n is a NON-NEGATIVE INTEGER etc....", being as n can be 0. Saying that it is an integer (rather than a number) also makes it explicit that it has to be an integer, although I'm sure most people would come to this conclusion regardless of whether the term integer or number is used. |
Bryce Thomas | Jan 10, 2010 | |
Printed | Page 249 Regexes |
On Page 250, you explained that a trailing line break adds an extra empty line, then how do you deal with a leading line break? Note from the Author or Editor: |
Yao G. | Sep 03, 2009 |
Printed | Page 249 3 regular expressions as the solution |
They match "\n2\n3\n4\n5\n" but don't match "1\n2\n3\n4\n5\n" (This \n means \r or \r\n or \n). |
Anonymous | Feb 19, 2010 |
Other Digital Version | 291 "Valdiate the Number" section |
In the epub version, after "Visa", none of the credit company names are listed with their displayed formats (as they are in the PDF version on page 275). |
Anonymous | Nov 21, 2010 |
Other Digital Version | 421 Solution |
Current regex "[^"\\\r\n]*(?:\\.[^"\\\r\n]*)" finds only one embedded escaped quote but will fail to match the whole string if multiple escaped quotes are present. We believe the correct regex should be "[^"\\\r\n]*(?:\\.[^"\\\r\n]*)*" . Note the extra "*" after the parenthesized expression. |
Paul Rubel & Dan Wyschogrod | Aug 29, 2013 |