in reply to Re: How to Debug the CGI Codes
in thread How to Debug the CGI Codes

For development, I even use:

use CGI::Carp qw/fatalsToBrowser warningsToBrowser/;

because it also handles warnings

Update: is wrong, see the posting from reneeb below

Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"

Replies are listed 'Best First'.
Re^3: How to Debug the CGI Codes
by reneeb (Chaplain) on Jul 10, 2006 at 09:01 UTC
    To handle warnings, you have to call the warningsToBrowser subroutine with a true argument. See documentation of CGI::Carp.
[reply]
[d/l]
Re^3: How to Debug the CGI Codes
by Ieronim (Friar) on Jul 10, 2006 at 09:06 UTC
    Just a note:
    warningsToBrowser(1) must be explicitly called after printing the page header, and will output all warnings as HTML comments. It's its difference from fatalsToBrowser, which catches all fatal errors (even compile-time!) without any additional actions. The CGI::Carp documentation contains additional info.

    UPD: i haven't seen the previous reply while writing this :)

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom