comment on

Yes, this crossed my mind but didn't make it into my text.

So long as the standard tools for creating modules are inserting "use 5.008" or such into every new module they help create, there is little point in CPANTS testers using older versions of Perl. I wouldn't be surprised if some CPANTS testers have abandoned using old versions because so many modules fail.

But I think a movement to remove these useless and annoying cases of "use 5.008" (as opposed to the few cases that are there for real and documented reasons) could motivate a CPANTS revival for older versions of Perl. It has certainly sparked my interest in setting up CPANTS for 5.6.0 and 5.6.1. I'm sure there will also be challenges in getting CPANTS running in such environments.

I'm also collecting the few, simple, fairly easy techniques that I use (or avoid) in order to keep my modules compatible with older versions of Perl. Perhaps even a perlage.pod...

- tye

In reply to Re^3: Artificial perl version dependencies (age) by tye
in thread Artificial perl version dependencies by rinceWind

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


The stupid question is the question not asked
	PerlMonks