Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re^4: CPAN modules on old versions of perl?

by revdiablo (Prior)
on Nov 28, 2006 at 17:21 UTC ( #586526=note: print w/replies, xml ) Need Help??

in reply to Re^3: CPAN modules on old versions of perl?
in thread CPAN modules on old versions of perl?

do CPAN authors know the minimum perl required for their modules?
I would hope so.

Really? It seems like kind of a lot to ask every CPAN author. Maybe I'm missing something, but I can think of two ways one would know the minimum version of perl required for their module:

  1. Know the details of each perl version well enough to predict what features their code uses will break and when those features appeared
  2. Try their module out on each successive old version until they reach one that breaks

Neither of which seem like viable options for the majority of CPAN contributors. Now, I would hope most authors know at least one version that their module works on -- that is, the version it was developed against. But that is not the minimum version.

  • Comment on Re^4: CPAN modules on old versions of perl?

Replies are listed 'Best First'.
Re^5: CPAN modules on old versions of perl?
by davorg (Chancellor) on Nov 29, 2006 at 08:39 UTC

    On further reflection I think you're probably right. I realised that I couldn't really tell you which version of Perl any of my modules need. I think I insist on 5.6 for most of them - but that's because I use "our" and "use warnings".

    Perhaps it would be useful if we had a list of the features that were added in each version of Perl. I don't mean just dumping the contents of the delta files, but something a bit higher level. Does anyone know of anything like that?


    "The first rule of Perl club is you do not talk about Perl club."
    -- Chip Salzenberg

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://586526]
[davido]: I am not finding closing STDIN to be an adequate means of making getlogin return undef.
[Corion]: Maybe doing a double-fork (daemonizing) can make go that information away, but maybe not
[Corion]: But I think my knowledge of unix/Linux datastructures is several decades out of date, so I don't really know what information it keeps on processes
[oiskuu]: The useful bits that relate to your process can be found under /proc/self. What information are you thinking of? Tty name?
[tye]: I just daemonized and getlogin() still knew who I had been.

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (8)
As of 2017-06-23 19:32 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (554 votes). Check out past polls.