Comment on

Superb write up.

I feel sadend however, by one thing that seems to be missing, but in my opinion is absolutely critical to any patch to any OSS Code Base -- test cases.

Even if you don't believe in Test driven development, even if you don't worry about having 100% code coverage in your test suite, the best way to explain what a patch does, is to provide some tests that demonstrates it's usage.

In reply to Re: Hacking perl by hossman
in thread Hacking perl by robin

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, 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, 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:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


Your skill will accomplish what the force of many cannot
	PerlMonks