in reply to Re: shebang arguments
in thread shebang arguments

Just because something is old and there's a new way of doing it doesn't mean that you should abandon the old. For one thing, 'use warnings' won't work on some older perls. If you care about them - and I do - then 'use warnings' is a bad idea.

I do 'use warnings' when developing my code, but I try to remember to remove it when I do a release. I usually forget and am prompted to do so by test failures being reported by the CPAN testers. Quite often those failure reports come from my own testing boxes :-)

Replies are listed 'Best First'.
Re^3: shebang arguments
by Argel (Prior) on Jul 03, 2008 at 22:13 UTC
    I agree that just because something is new does not automatically mean you should abandon the old method in favor of it. But on the other hand if a paradigm shift occurs then it likely means the new way is the better way. And in this case the impression I get is that the Perl community has shifted away from -w in favor of the warnings pragma. Hence why I called -w "old school".

    I think it goes without saying that you would use "old school" methods with older versions of Perl. That's part of what "old school" implies.

    P.S. Sounds like you should firewall off your test servers! ;-)