This looks like a good start.

I would add a couple of rules about variables:

• Variables should be commented unless clearly self-descriptive,
• Use a consistent variable naming style (I like lower_case_underscore_separated but some odd people prefer allInOneWordWithDanglingCaps,CONSTANT and Package_Variable can also be recommended),

And (of course!) I would argue with a couple of you rules :

14. Any reused code block above 5 lines must become a sub routine

5 lines can be a _LOT_ of code! The risk with that kind of rule is that some people might read it as "it's fine to cut'n paste up to 4 lines of code" or even "don't bother writing a sub that's less than 5 lines"

28. Do not use $_

$_ should not be abused but it has its uses and can make some blocks of code much clearer.

---

---

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.