Some suggestions:

3. no deliberate obfuscation

s/deliberate//

5. OO always to be used where possible

s/possible/appropriate/

6. Pass by reference

.= ' when appropriate'

9. Do not reinvent wheel always check CPAN

.= ' but do reinvent elliptic wheels'

19. All subroutines to be commented

s/commented/documented/

23. No Global Variables

s/Glo/Needless Glo/

24. use my not local

Repeats 23

28. Do not use $_

WTF? Why not? s/foo/bar/ for @xyzzy;

30. Initialise variables

Repeats 1

32. Where code returns a result it should do so or die with a meaningful error and $!

Always die? Even with errors that aren't fatal? 

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

In reply to Re: Perl Programming guidelines/rules by Juerd
in thread Perl Programming guidelines/rules by hakkr

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.