Re: (tye)Re: use warnings vs. perl -w

You're right, it does work, but I just tried this:

#!/usr/bin/perl -w
print "Content-Type: text/html\n\n";

$t = "hello world";
print "$h, $t";
[download]

It doesn't complain about $h being uninitialised. It does however, if you take out the HTTP header.

Update: I was running this on a Win32 webserver.

Is that the way it should be?

$code or die
Using perl at
The Spiders Web

Comment on Re: (tye)Re: use warnings vs. perl -w Download Code

Replies are listed 'Best First'.
Re: Re: (tye)Re: use warnings vs. perl -w by extremely (Priest) on Jan 25, 2001 at 08:53 UTC
If you are running under a webserver, the non-fatal errors my be hiding in the error log of your server or may even have been piped away to nothing, rather depends on the webserver. Check the error logs and see. -- $you = new YOU; honk() if $you->love(perl)	[reply]
Re: Re: Re: (tye)Re: use warnings vs. perl -w by Theseus (Pilgrim) on Jul 17, 2002 at 16:05 UTC
When I want to capture my warnings while running programs under IIS, I open STDERR to a text log file and then look in there for information.	[reply]
(tye)Re2: use warnings vs. perl -w by tye (Sage) on Jan 24, 2001 at 21:06 UTC
For me it complains either way, as it should. - tye (but my friends call me "Tye")	[reply]
Re^3: use warnings vs. perl -w by Anonymous Monk on Oct 29, 2012 at 12:05 UTC
These days, the -w command line flag is usually replaced with the warnings pragma, as the latter is more flexible, and has scope that is limited to the enclosing block, while -w is global in effect.	[reply]