i think this list cramps style too much, to a point of hindering development. while i agree that following a good set of coding standards leads to easier maintenance, i don't think this is the best starting point.

maybe something like:

• style
• follow perlstyle, except as noted below
• do not shift subroutine arguments, use code like my( $self, $arg1, @args ) = @_; instead
• name SCALAR, ARRAY, and HASH variables in the singular, not plural
• use taint mode
• ...
• substance
• untaint all passed parameters
• log all errors/warnings, using #your log module here#
• use CGI to process CGI parameters
• use DBI to access database
• use HTML::Template for HTML templates, not HEREDOCs
• ...
• tests
• write tests for each subroutine
• test modules for pod, using Test::Pod
• test for documentation coverage, using Pod::Coverage
• test modules for version information, using Test::Version
• verify all tests pass before merging code and tests with development stream
• ...
• docs
• document each module with pod, sections include: your sections here
• enter Change Request #(s) in comment upon checkin to SCM repository
• all code must be in SCM repository before release to ...
• ...

but i could be completely off base. it's been a while since i've developed these standards (or followed them in a large team.)

~Particle *accelerates*

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.