Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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

    • 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 the best practitioners think makes for good Perl.

      Putting all of this into a wiki is a knee-jerk good idea, but in reality doesn't have the same benefit. Sure, you may not agree with some of Damian's recommendations, but at least you can reason about what Damian's summarized and why you should deviate from that norm. Replacing that with a conglomeration of contentious permathreads on a wiki is much less useful.