Re: Get your script warnings on the page it generates

Another handy module that takes care of this for you (TMTOWTDI) is CGI::Carp. I've used it quite effectively for debugging in the past. I also like merlyn's idea of having them emailed to you -- I do that with my 404 errors, which gets obnoxious when your friends find out about it ;-)

use CGI::Carp qw(FatalsToBrowser);
[download]

-marius

Comment on Re: Get your script warnings on the page it generates Download Code

Replies are listed 'Best First'.
Re: Re: Get your script warnings on the page it generates by chipmunk (Parson) on Jan 18, 2001 at 22:30 UTC
But warnings aren't fatal... `use CGI::Carp qw(fatalsToBrowser);` will send die/croak/confess messages to the browser, but not warn/carp/cluck messages.	[reply] [d/l]
Re: Re: Re: Get your script warnings on the page it generates by marius (Hermit) on Jan 18, 2001 at 22:51 UTC
Good call, chipmunk. I presume you could use carpout() from CGI::Carp to redirect warn/carp/cluck calls to STDOUT. Additionally as of CGI::Carp v1.20: `use CGI::Carp qw(fatalsToBrowser warningsToBrowser);` [download] With this, you can call warningsToBrowser(1) to past warnings to the browser after the call. Being proven wrong is one of the best reasons to go RTFM, I guess. =] -marius	[reply] [d/l]