I will admit I mispoke. I meant to say that my original reply to your post got messed up. It seems that when I thought I was replying, I was in fact replacing my first post.

I am not sure what you mean by the term "flaming", however, if I did it, it was truly unintentional.

I found it difficult to understand how you expect me to know what the author does with his money. I do not know many people that could give such information. Also I do not feel that it should play any part in whether or not you buy a book that has good information in it

As for the chapters being clear, well obvious to me, but maybe not to others, this is my opinion. I thought that was what a review was. I did not realize that I should give a list of each chapter. Or is that not what you were asking for?

When I said that the code is how Perl should be, I was trying to convey the fact that it followed the strictest format and is written as most Perl programmers try to get their code to be. It is clear. Not obfuscated at all. Does not seem to have any unecessary code in it and as it is in use in a few classrooms that I know of I would say it is a good reference. Again, this is my opinion.

I must admit that I read quite a few of the other reviews and several of them lacked the detail that you wanted from this review. I will apologize for the comment regarding the dimensions. That was uncalled for and I am sorry. To me your first reply seemed very insulting and I took it more personally than I should have. If I post anything in the future I will try to make it more useful. Kerry

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.