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.

OSCON 2006, Day 2: More Perl Best Practices 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Not just Damian's (Score:2)

    by Damian (784) on 2006.07.26 9:35 (#48998)
    Perl best practices are really Damian's Perl practices.
    Some of them certainly are. Mainly the ones related to layout, which I did point out up front: "DON'T MATTER" ;-)

    However, whether they were specific to me or more generally agreed upon (in the introduction to the book there's an extensive list of well-respected Perl developers who contributed to the final set of recommendations), every suggestion I made is based on providing solutions to genuine problems and/or traps in Perl. I also pointed out that I didn't expect everyone to agree with everything, but that everyone did need to at least think about the issues I was raising and address them in some way.

    However, he has gone to great lengths to create compelling arguments for each of his practices. For this reason, I intend to at least give each of Damian's practices a chance.
    Thank-you. That's all I'd ever ask. Whether you ultimately change any of your existing practices or not is far less important than the fact that you are re-examining them. You may find they work fine for you, as is; you may find some of my suggestions improve your programming life; or you may find a third way that meets your needs even better. Any of those three alternatives is a great outcome.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.