Wiggins d'Anconia wrote:
use strict; # always use warnings;# usually
Why not always? I would make it:
use strict; # always use warnings; # always
I won't argue with you over them. I always do both... some people don't like that "always" on the warnings, so I use the "usually". I disagree about warnings being more important than stricture, but again that isn't likely to lead us anywhere important considering we both agree that they are both helpful and should be on :-).
Actually, I didn't mean that the warnings are more important, but that they will never break any program which otherwise works without them, so while indeed being less important as they don't affect how the program runs, they for the same reason are easier to use giving less of a reason to not turn them on. (What a sentence... Sorry, I'm in a little hurry...)
Though I do seem to have a problem and maybe someone here can enlighten me or suggest why or a fix about the warnings when running under CGI. If I have a script that generates X number of warnings then Apache or the script seems to hang in an infinite loop and does not return any result, despite the fact that the script will execute to completion. I generally have to kill the runaway process, then once I have fixed the warnings (that appear normally on STDERR in the apache error log) the script works fine with no further changes. Any ideas why warnings going to the error log would hang the process?
use CGI::Carp qw(fatalsToBrowser warningsToBrowser);
-- ZSDC Perl and Systems Security Consulting
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
