Ahhh, you are talking about the quality that cannot be named :) I can't tell you what good practices are, but I can tell you that I know them when I see them.

My advice would be to stick around and read. Read some of the modules that you download from CPAN. After a while you will begin to get a feel for things you like, and things you think stink.

Not to mention that one person's good practice is another person's poison. Just ask about whether one should leave off return at the end of a subroutine, or whether it's better to say $bar and foo() or foo() if $bar. Or even if( $bar ) { foo() }. It depends on the circumstances.

- another intruder with the mooring of the heart of the Perl

In reply to Re: The Tao of Perl by grinder
in thread The Tao of Perl by Mago

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.