If this is not enough info I can measure my copy to provide you with the dimensions

Your original review was in fact 4 short sentences and said next to nothing. My post was simply a suggestion that in order to be useful, the review should be more in-depth. I then posed a number of questions that you could answer to improve the review. This all should have been viewed as constructive criticism and either used to improve your review, or ignored and possibly countered if you felt it would not improve your post.

The book itself is divided into 16 chapters, all of which are simple, easy to understand, and concise and clear.

I could ask, how are they clear. I could ask for examples of the clarity. I could ask for what the sections actually cover. I could ask how well they cover them and if there are any deficiences.

The code is exactly how Perl is meant to be.

I could ask what exactly "Perl is meant to be." I could ask if this means the author uses strict and warnings. I could ask if it fits its intended purpose (ie to teach) and is not unecessarily complex. I could ask thousands of other questions, but honestly, I don't care and I doubt they'd be used by you to improve anything.

So in conclusion:

1. If you're going to post something, make sure it adds something of value.
2. Accept constructive criticism as what it is intended to be, constructive. Flaming your critics will just deprive you of their assistance.
3. If you do post something without worth and choose to change it at a later date, at least place an accurate update notice. Changing a post and misrepresenting its original content is extremely bad form.
4. I don't care if you follow the above advice. You're the only one that loses.
5. I shouldn't have bothered to write this reply, it's a waste of my time, may as well post it now though.

Adios.