On Thu, May 19, 2011 at 4:11 PM, ynon perek <[email protected]> wrote: > Hi, > As much as I like writing new code in 5.14 (the use re '/xms' pragma really > bought me), I must agree with some of the things said here. > > When you have tens of thousands lines of old code (global vars all around, > using ancient bugs, and works by magic because too many people have hacked > too many edge cases), it's extremely frightening to upgrade. > > Most of the organizations I work with still use 5.8.x. For new code (and > when possible), we install perlbrew and run the new code in a new > environment, but since most old code has no testing, running it under newer > versions may or may not work, and the failure may not even be visible. > > On an ideal world, all code would have unit testing, and no one will ever be > afraid to upgrade :)
So let me connect this to another to a related question. Do you run a "supported" version of your operating system? If not, and if you don't watch closely then your computer is probably vulnerable to all kinds of simple attacks. If you (or your company) sticks only to supported versions of your OS then sooner or later they will upgrade the OS. With that tons of things will be upgraded that your system uses. Including your database and perl. So sooner or later you will be forced to upgrade. Is there any preparation made for that? BTW here is the link to the TPF Survey from a year ago about the versions of perl people are using: http://survey.perlfoundation.org/Data-PerlSurvey-2010/R/07_perl_info/index.html Gabor _______________________________________________ Perl mailing list [email protected] http://mail.perl.org.il/mailman/listinfo/perl
