If part of your purpose for posting code is for others to send you fixes, then it will help greatly to embed a file version stamp in each file. That provides a way for people to do a quick check to see if the module they just reviewed or extended has been updated, and it provides you with a quick check to see if submitted code is based on older versions of files. Any decent source-code control system will provide a way to embed a version string in a file.

Your cause is also going to be helped by having a complete test suite corresponding to each package you're publishing. You can then enforce that any submissions need to pass the published tests, and that any newly submitted functionality needs to be covered by new tests. It also provides a backstop to help prevent your posting broken code.

---

---

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.