in reply to Running with warnings on a remote server

There are a couple of ways which you could achieve this ...

 

Ooohhh, Rob no beer function well without!

Replies are listed 'Best First'.
Re: Re: Running with warnings on a remote server
by Fastolfe (Vicar) on Nov 04, 2001 at 21:11 UTC
    CGI::Carp is actually a bit more powerful than that, even. Some examples (some from the docs):
    # Send warn/die messages to a separate log file BEGIN { use CGI::Carp qw(carpout); open(LOG, ">>/usr/local/cgi-logs/mycgi-log") or die("Unable to open mycgi-log: $!\n"); carpout(LOG); } # Or, normal fatalsToBrowser behavior but catch warnings also use CGI::Carp qw(fatalsToBrowser warningsToBrowser); use CGI qw(:standard); print header(); warningsToBrowser(1); # enable warnings to browser
    Nifty stuff!