in reply to Re^3: $^W or require warnings and import warnings;
in thread $^W or require warnings and import warnings;

Having a separate perl seems a lot easier to me than examining every new script you put on the machine to make sure it's going to work with your legacy perl.

Sure ... if you're even allowed to install a new perl on the machine. Often political or social concerns override the obvious technical solutions. Especially when "legacy systems" are concerned.

  • Comment on Re^4: $^W or require warnings and import warnings;

Replies are listed 'Best First'.
Re^5: $^W or require warnings and import warnings;
by bluto (Curate) on Jun 16, 2005 at 15:37 UTC
    It's just hard for me to understand that you'd have the freedom to upgrade your development method to Subversion, but not be able to install your own private copy of perl. I thought I had strange politics to deal with at work ... I've seen risk-adverse behavior wrt maintaining legacy systems, but usually there is some consistency to it. :-)