Re^5: Perl module to get warn or die to render as HTML

I don't mind leaving FatalstoBrowser on either because I, too, program mostly just for internal customers. I like your term "warning chaff."
The stuff I see that irks me is stuff like the following line, repeated with the exact timestamp and line numbers/FH names like 20-50 times:

[Mon Sep 25 15:33:37 2006] securityQuery.cgi: Use of uninitialized val
+ue in concatenation (.) or string at /var/appl/httpd/cgi-bin/ms/secur
+ity/securityQuery.cgi line 154,  FILE  line 122.
[download]

Sorry, feeling a little grumpy today. Also I used to be one of the worse offenders.

I just thought of one last tip--if you do use CGI:Carp and want to send warnings to the browser, don't forget to put your

warningsToBrowser(1);
[download]

statement after you've written the headers.

_________________________________________________________________________________

I like computer programming because it's like Legos for the mind.

Comment on Re^5: Perl module to get warn or die to render as HTML Select or Download Code

Replies are listed 'Best First'.
Re^6: Perl module to get warn or die to render as HTML by ptum (Priest) on Sep 26, 2006 at 14:20 UTC
Right. But in most cases, warnings like the one you cited can and should be corrected in production code -- if you're trying to manipulate a value and it is undefined, then you haven't really trapped for the possibility that the value you're handling is somehow not yet populated, which can lead to more serious problems.	[reply]