The most important thing to have any "progress" happening is having something to do the actual work. You can discuss for months whether some new idea needs to be implemented in core or in a module, if noone is actually going to implement the thing, all the discussion is moot.

The current feeling on p5p seems to be like this:

• If it can be implemented as a stand-alone module as easily as in core, put it on CPAN.
• If it's "big", and it can be implemented as a module in any way, and the point above doesn't apply, first implement it as a module. Only when usage has flushed out all kinks, and actually have shown a need, inclusion in the core may be consideren.
• If you have a patch, and regression tests, and you can convince p5p it's a good idea, and it doesn't slow down current code too much, and it doesn't break existing code^† and any of the points above don't apply, it may be included in the core.
• If it's a bugfix or performance improvement, it's likely to go in.

^†Actually, code gets broken all the time. p5p just tries to be very careful, weighting the benefits of a new feature to the likelyhood of code breakage, and if all possible, have a full deprecation cycle. (So, if you have a patch that breaks something in 5.12, 5.14 will have the old behaviour but with a warnings, and the new functionality will be in 5.16).

---

---

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.