comment on

As for me, i only use Perl versions that are still maintained. For some stuff, i decide early on that i want to use certain features of the latest version of Perl.

I know this might sound a bit harsh, but life is too short. If you want to run the latest versions of my published modules on a 12+ year old, unsupported version of Perl, why should i have the burden of backporting and testing against a Perl version that i will never again use for myself (and have banned from my systems because of all the unfixed security bugs). I would certainly be willing to explain what parts of my code do to help you make that backport. But otherwise, i'd rather spend my time writing new code and enhancing existing one.

I'm a software developer, not a museum curator.

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP

In reply to Re: Is there a concerted effort to break CPAN for older perl versions to drive support for v7? by cavac
in thread Is there a concerted effort to break CPAN for older perl versions to drive support for v7? by Anonymous Monk

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.


Perl: the Markov chain saw
	PerlMonks