All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

I laughed, cried, fell down, my life was changed. Well, maybe I didn't cry so much;-).

Seriously though, best perl book since I first picked up the Camel. Any project that uses PBP as a guideline is doing at least one thing right.

In a way it's a shame this came out in this form though. I'd imagine that a guide to perl best practices could best be implemented in a wiki, with arguments for and against certain practices as well as updates and additions from the community. The book would be a perfect baseline to start off from, but somehow I can't see O'Reilly/TheDamian looking too favourably on someone who'd copy the entire book into a wiki;-).

In a way it's a shame this came out in this form though. I'd imagine that a guide to perl best practices could best be implemented in a wiki, with arguments for and against certain practices as well as updates and additions from the community.

PBP (any "best practices" in general) works best when it comes from a single voice. Damian synthesized a lot of experience when he condensed it into a dead tree. So this isn't one lone kook's guide to what makes for good Perl, but a coherent guide to what some of th