Top critical review
15 people found this helpful
No, no.. skip this for "Perl Best Practices"
on January 3, 2012
First, this book, at least in the Kindle edition, is very poorly edited. I don't think it's a kindle issue, because I'm not talking about the wretched formatting, lack of T of C in the kindle edition, because they only charged $3 for it.
But there are just too many things that are either code typos or explanatory sentences that don't make sense. A couple of examples:
1) The author is talking about auto-incrementing of strings, and says that "While ZZ9 becomes AA0, ZZ09 becomes ZZ10..." Nooo, ZZ9 becomes AAA0. Not a big deal, but typical.
2) There is an example of initializing an array with a list, such as:
my @cats = ( 'Daisy', 'Petunia', 'Tuxedo', 'Jack', Brad' );
The author then says: "Remember that the parentheses do not create a list. Without parentheses, this would assign Daisy as the first and only element of the array, due to operator precedence."
Huh? What's he trying to say? His point is that the parentheses are essential to creating the list, for the reason that he specifies, yet he says that they "do not" [ in italics] create a list.
3) In "Perl Best Practices", the author when suggesting a best practice, carefully explains why. This author just says "... prefer this way... " as though we are to take him at his word.
I'm not suggesting that this author doesn't know his stuff, just that there are too many obvious code errors in this that should have been caught, along with very poorly edited explanations. I realize that the examples above are trivial, but for just that reason they should have been caught.