> > Perl 5.20.0 was released in May and is considered stable.
Yes. > In addition to > missing out on a number feature enhancements by using 5.8.8, Of which there have been quite a few in 5.10, 12, ... 20. Also, CPAN modules are slowly giving up support for 5.8 & 5.10, so if you are updating modules, you'll be forced to update Perl eventually. > I'd personally recommend upgrading, but, as always, doing so carefully. > My usual plan would be: update one Development node; test; and spread to more DEV nodes. Do not upgrade PROD nodes under working legacy code; upgrade their Perl's when code tested with the new Perl are deployed. > There are a handful of undocumented features and reliably buggy behavior > from 5.8.8 that have been removed. See "Incompatible Changes" and > "Deprecations" in the deltas. Chances are you're not actually using any, > though. > Note that you need to read each major release 10..20's perldelta.pod . There's a very good chance if he's using Test::More that he *is* using the predictable order in hashes, if so random hash ordering will break his tests (but not his code). One nice new feature is that nice new features are tagged Experimental and will WARN unless explicitly used, to avoid the smartmatch "you didn't warn us" problem again. Note also that some core distributions (e.g. CGI.pm) are no longer core, > and may need to be installed directly on your deployments, depending on > your codebase. > > For more information on 5.20 specifically, I'd recommend viewing Ricardo > Signes' presentation on it at YAPC::NA a few days ago: > https://www.youtube.com/watch?v=D1LHFKGHceY > > Too bad you missed my discussion of the 5.20 deprecations and the delightful synergy of new features (in core and List::Util) earlier this month. (I posted some notes, mostly links to Delta and youtube.) -- Bill Ricker [email protected] https://www.linkedin.com/in/n1vux _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
