Re: Perl's changes in the use of packages

Replies are listed 'Best First'.
Re^2: Perl's changes in the use of packages by choroba (Cardinal) on Jul 06, 2017 at 20:06 UTC
I'm not sure what's the OP's benefit, but I've witnessed the drawbacks of not doing so: You can't use modules from CPAN, at best you need to search backpan for old versions (in my case, our client switched from FTP to SFTP); You can't switch to a new OS version or architecture smoothly (see The Unicode Bug with Transliteration or Substitution for an example); Old security bugs lurking (hash randomization etc.). ($q=q:Sq=~/;[c](.)(.)/;chr(-\|\|-\|5+lengthSq)`"S\|oS2"`map{chr \|+ord }map{substrSq`S_+\|`\|}3E\|-\|`7**2-3:)=~y+S\|`+$1,++print+eval$q,q,a, [download]	[reply] [d/l]
Re^3: Perl's changes in the use of packages by 1nickt (Canon) on Jul 06, 2017 at 23:30 UTC
All valid points. I am of course not suggesting to never update your Perl version. But I would think that for the OP, given how he described his code, keeping up with the very latest Perl might be unnecessarily far in the other direction. The way forward always starts with a minimal test.	[reply]
Re^2: Perl's changes in the use of packages by Anonymous Monk on Jul 07, 2017 at 19:24 UTC
Some have already said what the benefits are, but in our case, it's driven by those sysadmin who rule by fiat and must always upgrade to the latest version of this or that OS. So, we must roll with it.	[reply]