Many of your "best practices", as pointed out by others, are simply style guides. Hack out a Perl::Tidy configuration the team is happy with and most of that stuff is taken care of. Oh, you might still want to impose local constraints on identifier construction and stuff of that nature, but those really are not Best Practice items.
You may also find Perl::Critic is a helpful tool.
BTW: I find statement modifiers read very nicely. They break the flow much less than the same statement broken into two parts by forcing half of it into a block. A single succinct entity is easier to comprehend than the same code broken into two disparate parts.
True laziness is hard work
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||