Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Re^3: Stop suggesting to upgrade perl

by chromatic (Archbishop)
on Sep 04, 2013 at 00:41 UTC ( #1052200=note: print w/replies, xml ) Need Help??

in reply to Re^2: Stop suggesting to upgrade perl
in thread Stop suggesting to upgrade perl

... certainly doesn't justify (in my mind) requiring the use of 5.10 as a minimum version in a CPAN module.
But it must be borne in mind that there can be considerable time and expense involved for a company to (run a reasonably recent version of Perl)...

You want CPAN authors who give away their code for free, largely in their volunteer time, to test their code against at least a dozen and sometimes as many as seventeen or eighteen stable releases because it's too expensive for a business to upgrade to a supported version of Perl? You object to me using features I personally added to Perl itself several years ago in my CPAN code because it's too expensive for your business to install a new version of Perl more often than once every five years?

I can understand why you might want that, but why would I do that?

Replies are listed 'Best First'.
Re^4: Stop suggesting to upgrade perl
by Tux (Abbot) on Sep 04, 2013 at 07:58 UTC

    Only 18? I test Text::CSV_XS with all supported perl versions ever released, both in threaded and unthreaded version on as many OS's as I have access to. That is currently over 120 builds and tests before I release.

    External USB-drives work well for that purpose. I think in now has over 150 versions of perl installed for my laptop architecture.

    What you did not mention however might be way more important with CPAN modules: testing on different architectures and operating systems. What works well on Linux is not guaranteed to work on Windows, NetBSD, HP-UX, AIX, MacOSX, AIX, or OpenVMS. What works well on i686 might not work on ia64, pa-risc, risc, or arm. It is impossible for CPAN authors to test every version of perl in any possible configuration on every supposedly supported OS and version thereof for there to be released module. Feedback is vital. CPANTESTERS is a big help, but no guarantee.

    Next time when you hit a bug, consider doing some analysis yourself and post a patch in your RT ticket, so the author is able to improve portability.

    Enjoy, Have FUN! H.Merijn
Re^4: Stop suggesting to upgrade perl
by boftx (Deacon) on Sep 04, 2013 at 05:38 UTC

    Chromatic, your post deserves a well thought out response which, at the moment, I am too tired to properly compose. I will read this again and attempt to give it the justice that you so justly deserve. Please be patient with me.


    I suspect that it is often the case that those who write the code at a company don't have as much control as they would wish for what platform is in use or how upgrades are scheduled. And while you might be justifiably perturbed about companies that use expense for a reason to not upgrade for a very long period of time, it is not unreasonable to go three years or so. (Yes, five is stretching it even for me, but I have seen it on more than one occasion.)

    On the other hand, I would not be surprised to find employees of those companies contributing to CPAN in an effort to pay-it-forward. I know that I have tried, and have seen others do so at every company I have been associated with for the last 15 years.

    Oh, we mustn't forget that in many cases it is simply that someone is following the age-old adage that if it ain't broke, don't fix it. :)

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1052200]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (4)
As of 2018-06-24 05:47 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (126 votes). Check out past polls.