Heh, a couple different reasons:
in reply to Re: Daemon possessed perl
in thread Daemon possessed perl
I learned a ton about many aspects of Perl from this book, and found it easy to understand (perldoc is not always easy to understand :)I have enjoyed other of the same authors books and modules, and supporting his efforts might keep him writing :)The book actually has a daemon module (several actually) and walks you through different revs of the module as features are added, as well as showing More Than One Way To Do It. This encompasses not only what perldoc does, but gives a great understanding on how to fit all the pieces together.
While I agree that perldoc can answer many questions, and I don't want to belittle it as a resource in any way, the original poster seemed to be new to the topic in general, and the book would provide a clear picture of what they were dealing with, all in one package. With the docs you may be going back and forth to several different topics and possibly missing things, as well the possibility of missing important security concerns rises dramatically without a bit more of a big picture view.
To close I should say that, while books are a great source of information, the concepts should be sanity checked with the documentation. Books may have been using older revs of modules, perl, and OS's. Also, books may have been written before important security issues or other bugs were found, and may not address those issues as well as the docs with your latest distro. Be smart, use all the available reference material you can!
"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!