I'm going to have to post in disagreement.
When I first started Perl, I got the Camel book, and had no problems
with the first half. (The latter half, discussing blessed objects, references, etc, went a bit over my head at
the time. When I started reading the Panther book (Advanced Perl Programming), I
again got the first half, which happily covers that latter half of the Camel book.
The second half of the Panther book was too much for me.
After a while, I started working with GUIs in Perl, and Networking, and I returned to the Panther
book, only to find that it was too skimpy. People unfamiliar with
sockets will not be able to program based solely off of what they
find here, while people familiar with sockets really only need to
have a few functions pointed out. The author has a tendancy to answer every question with parts
of a custom module, which don't address the question well enough to
give you an answer to a related-but-different question. The GUI section
in particular suffers from this. Programmers experienced with
callbacks and the like will need little more than a function listing, and
those that aren't familiar with it will not find the fundamentals explained here.
As I said, I learned a lot from the first half, but now the Perl Cookbook, and the perlman:perlobj, perlman:ref, and perlman:perlboot pages
cover everything in better detail.
You said My only persuasion against buying this book is that is is not for beginners.
Which is true. It isn't for experienced programmers either. It seems to try to bridge the gap, and fares poorly IMHO.
| [reply] |
I've had no formal network, nor GUI learn'n. Additionally, I hadn't seriously
touched either until Perl. The Panther along with the man pages was enough
for me to feel confortable and get through networking. I still have yet to do
GUI, but the Panther makes it seem easy enough.
I don't know if this fits or not with your description. I consider myself
an advanced programmer on certain levels (such as algorithms and program
structure), but a novice on some specific aspects (GUI design, device specific
programming).
But I appreciate your feedback, as it gives a good contrast to the review.
Which I admit, was a tad bubbly :) .
Cheers,
Gryn
| [reply] |
I would like to comment that the portion of the book on persistance and relational databases is very well done. This would allow someone who is familiar already with databases to quickly use Perl to make modifications to their database. When I was learning DBI/DBD I had a bit of a hard time finding useful examples. I would recomend this book to DBA's who are looking to expand their knowledge of Perl and possibly use it to assist them in doing their jobs. While this book is not an exhaustive book on DBI(there are other books for that "Programming the Perl DBI" is good for focusing on DBI) if a DBA had to choose one book between the two this book would allow them to get to work with database access as well as introduction to the other powerful things that Perl can do.
| [reply] |
These days this book feels really dated to me in many places, like it's just screaming out for a new edition. | [reply] |
I havent read the whole book yet but the parts that I read really helped me get to a higher level of Perl. I knew sockets etc. but the reference section was very helpful.
I agree with swiftone on Perl having the single most amazing documentation that I have had experience with - reading the Perl documentation alone makes buying books an extra thing (instead of a neccessity).
| [reply] |
I'm in the process of reading this book and read almost first half of the book, this is the book I have been searching for 2 years.
I recommend this book after reading the books like, learning perl, intermediate perl.
This is book is following a wonderful tutorial-istic approach, a must read and a must have book in your(our) perl library.
UPDATE:
I have learned to use the typeglobs effectively after reading this book.
I am talking about the book authored by Sriram Srinivasan.
| [reply] |
| [reply] |