in reply to Perl 64-bit versions
Sorry I do not emphasize on Windows, but I'd like to share my thoughts too.
First off, anything 5.10.1 and up is fine with me. I really want defined-or in my code, but as I was able to patch perl-5.8.x, I had that since 5.8.1. All below 5.8.4 is crap when you want Unicode support.
The way 5.14.x and up deals with charnames and Unicode was a reason for me to upgrade to 5.14.1 and I ran into no serious problems perl-wise. The problems I ran into were module related: e.g. the newest version of DBD::Oracle only works with Oracle-10 and up. My box had oracle 9. Then one has to dive to BackPAN to find the last module that works with a new perl and an old environment. That is what is taking long long long time and is no fun, certainly if the maintainer of the module switched somewhere between the working version on your previous perl and the not-working version on the new perl.
I never enable old perl trees in my new environment. I build perl to ignore old trees, so I can remove them when all tests passed. Not only to keep the disks clean (I have to copy most of it to customers too, and having a sanatized tree makes that a lot easier to do), but also this forces me to test every module I use on the new perl.That said, with so many modules to install, you should have a look into cpanprefs and make a "Bundle" of what you have now and install the Bundle into the new perl. If you make the right preferences to cpanprefs, a single cpan command can run for up to 50 hours unattended! (been there, done that).
Enjoy, Have FUN! H.Merijn
|Replies are listed 'Best First'.|
Re^2: Perl 64-bit versions
by BrowserUk (Pope) on Mar 13, 2012 at 16:38 UTC