Errata for Programming Ruby 1.9 & 2.0 (4th edition)

#51186: There is an example called "Book In Stock" in this chapter. "The row contains the book’s ISBN and price". But in the following sample csv (on page 29), the last column has been named "Amount" ( "Date","ISBN","Amount" ). And so is sample code on page 38 , "row["Amount"]", and "we extract the data from the ISBN and Amount columns" on page 38, and "row["Amount"]" on page 39. All other place are using "price" in both sample code and text. Suggest to replace “amount” with "price"--Clark Wang

#51187: The "Inheritance and Mixins" section has been placed in a chapter of "Modules", I think this section is irrelevant to "Modules". In the Kindle version, this section is before the chapter of "Modules".
And at the end of this section, "We’ll explore mixins a little later on page 77.", actually, this section IS on page 77, it references(links to) the page that itself is on.--Clark Wang

#51445: Named matches only set local variables if the regular expression is on the left side of the expression (i.e., /RE/ =~ string). This paragraph did not make it clear that this was the case:

The named matches in a regular expression are also available as local variabless. (This works
only with literal regular expressions. You can’t assign a regular expression object to a variable,
match the contents of that variable against a string, and expect the local variables to be set.)

See: (http)//ruby-doc.org/core-2.0/Regexp.html#method-i-3D-7E

Also, on page 110 of the PDF, there are several examples with named matches with the RE on the right side of the expression. I think it would be better to switch the RE and string so people coming from a perl background (like me) would be more inclined to migrate to the preferred Ruby RE style.--Bruce Albrecht

#51518: In section 22.13 Paragraph 2:

"Braces have a high precedence; do has a low precedence. If the method invocation has parameters that are not enclosed in parentheses, the brace form of a block will bind to the
last parameter, not to the overall invocation. The do form will bind to the invocation."

I can't get my head around this easily, an example would really help.
--Tim Passmore

#51319: In the PDF version of the book, it would be really handy if methods named in the "Mixes In" section of the class documentation were linked the their documentation instead of just being dead text.--David Hull

#51225: You neglected to include the index in the epub (and presumably mobi) version of the book. This is quite disappointing, as (especially with a technical book) the index is a very valuable resource. Tagging the references to create an index that links to the paragraph level can be tedious, but it's worth it. If that's not an option, you should at least link to the print page (easy enough to target <span id="pg235" /> and RegEx the page references in your index)--Tom McCluskey