At 02:58 PM 6/15/01 -0400, Tim Musson wrote:
>Hey all,
>
>I have been using
>#!/perl -w
>
What about using "use warnings" rather than the "-w"?
It seems that I read in Programming Perl to use "use warnings" but it all
seems foggy now.
Are the two the same thing?
>and based on some posts have started using
>use Strict;
That's use strict; (little s)
>use Diagnostics;
little d
>as I develop code (all helpful things to do).
>
>My question is when I put the code into production, should I leave any
>of these turned on? I am thinking that they are to help with
>development, so why run the extra code in production, so have been
>turning them off, but wanted to ask and find out for sure.
You should leave strict on, since almost all of its effects come at compile
time. There are differing schools of thought on leaving -w in for
production (and therefore there will likely be a religious flamewar in
response to this question). If you can afford the effort, something like
Randal's fatalsToEmail is a good idea (look under
http://www.stonehenge.com/merlyn/LinuxMag/col14.html).
--
Peter Scott
Pacific Systems Design Technologies
http://www.perldebugged.com
