Small Mosaic


Categories:

/books
/career
/codinghorrors
/events
/geekstuff
/justdont
/languages
/languages/bash
/linkshot
/magazines
/meta
/misctech
/movies
/nottech
/operatingsystems
/operatingsystems/linux
/operatingsystems/linux/debian
/operatingsystems/solaris
/perl
/presentations
/programming
/python
/ruby
/security
/security/apache
/security/tools
/serversmells
/services
/services/dns
/sites
/specifications
/sysadmin
/testing
/tools
/tools/commandline
/tools/firefox
/tools/gui
/tools/network
/tools/online
/tools/online/greasemonkey
/tools/puppet
/unixdaemon

Archives:

July 20101
June 20104
May 20102
April 20101
March 20108
February 20101
January 20102
October 20092
September 200910
August 200910
July 20094
June 20091
April 20093
March 20097
February 20094
January 200917
Full Archives

Tue, 05 Sep 2006

Perl Debugger Pocket Reference - Short Review
A book about a debugging program is never going to be that exciting. At best it'll be both comprehensive and concise, two things that don't have to be mutually exclusive, at worst it'll be a dull rehash of the perldoc. Which type is this one?

The Perl Debugger Pocket Reference (PDRB) starts with some basic practises to help you avoid debugging (the usual use strict and use warnings) before walking through two very basic debugger sessions and then on to the bulk of the book, the command reference.

It's hard to judge this section of the book, most people will only read through it once (if that) and will probably just dip in when they need to look something up. The commands are broken up by function, not listed alphabetically, which can be annoying but does let you look for better ways to do tasks. The explanations are clear and the examples are mostly useful so it's functional if dull.

PDRB then finishes up with a short introduction to the DB and Devel namespaces, what they do and how you can use them to write your own debugging modules. The coverage of this last bit is well written but very light weight - it shows you what's there, not how to make the most of it.

Down-sides? The biggest example in the book (the linecounter.pl script) is off by two lines in all the examples I tried; which is annoying when you're trying something for the first time and have no idea why it isn't working. I'd also like to see a couple of longer debugging sessions, a couple of pages each, with some of the more advanced functions illustrated.

Score: 6/10. Nicer than the docs but an occasional dip in to rather than an actual read.

Like this post? - Digg Me! | Add to del.icio.us! | reddit this!

Posted: 2006/09/05 20:11 | /books | Permanent link to this entry | This entry and same date


books career codinghorrors events geekstuff justdont magazines meta misctech movies nottech operatingsystems/linux operatingsystems/linux/debian operatingsystems/solaris perl presentations programming python ruby security security/apache security/tools serversmells services/dns sites sysadmin testing tools/commandline tools/firefox tools/gui tools/network tools/online tools/online/greasemonkey tools/puppet unixdaemon

Copyright © 2000-2010 Dean Wilson XML feed logo