in reply to use warnings vs. perl -w
Under Windows you should start all of your scripts with
Surprised? Note that this won't tell the operating system to look for perl.exe in the /usr/bin directory. It will tell perl to turn on warnings, even on Windows, even without Apache. Oh, when using Apache, you'd want the real path to perl.exe instead of /usr/bin/perl, since, as you know, Apache looks at the #! line.#!/usr/bin/perl -w
I don't use warnings as that will prevent my code from compiling prior to Perl 5.6 and it is still way too early to yell at anyone for running pre-5.6 versions of Perl. (:
- tye (but my friends call me "Tye")
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: (tye)Re: use warnings vs. perl -w
by $code or die (Deacon) on Jan 24, 2001 at 20:59 UTC | |
by extremely (Priest) on Jan 25, 2001 at 08:53 UTC | |
by Theseus (Pilgrim) on Jul 17, 2002 at 16:05 UTC | |
by tye (Sage) on Jan 24, 2001 at 21:06 UTC | |
by Anonymous Monk on Oct 29, 2012 at 12:05 UTC | |
Re: (tye)Re: use warnings vs. perl -w
by dug (Chaplain) on Jul 17, 2002 at 16:35 UTC |
In Section
Seekers of Perl Wisdom