matze77 has asked for the wisdom of the Perl Monks concerning the following question:

Hello Monks!
Should i -as a perl beginner-,
know more restrictions, use this in my programms besides:

use strict; use warnings; use diagnostics; #more verbose than warnings note: only use it till + program is failure free ...

I ask this cause i want to prevent bad habits (to which i tend much i fear ;-)) ...

Other tips which make perl coding easier, besides security you think are useful are welcome too, ofc.

(Someone mentioned a Module for correction of Typos, but dont recall / find it maybe it was on CB ...)

Thanks in Advance
MH
<update> use diagnostics added to code </update>

Replies are listed 'Best First'.
Re: Guide to good coding, security, safety options tests ...
by moritz (Cardinal) on Dec 02, 2008 at 10:59 UTC
    I recommend reading perlstyle.

    There's also TheDamian's book "Perl Best Practices", which are surely worth a read, although some of the advices are controversial. Perl::Critic is inspired by that book.

Re: Guide to good coding, security, safety options tests ...
by brsaravan (Scribe) on Dec 02, 2008 at 12:26 UTC
    You can use this link for better coding guidelines PerlCritic.
    Ofcourse, this is purely based on Perl::Critic module.
Re: Guide to good coding, security, safety options tests ...
by oxone (Friar) on Dec 02, 2008 at 15:09 UTC