Re^2: How to conditionally use CGI::Carp?

in your CGI scripts and not in your modules, it should work fine both ways

well, actually, no... at least, not for me. I assumed this as well, but lots of experimentation has shown otherwise. For example, in February, I posted Inconsistent results from CGI::Carp handler, to which no one at all has replied. In my own research (which I haven't yet completed, but am getting close), I find that some/many perl errors inside MODULES are not caught by the CGI::Carp handler when the "use" statement is in the main (non-module) perl code (even within BEGIN blocks). However, if I duplicate the code within the modules, then the perl errors are caught and sent to the browser as expected (or to wherever you redirect).

This is the reason for this current thread. If I didn't have to put the "use carp" stuff in the modules, none of this would be of concern.

...and the problems/confusions just seem to be adding up. For example, where are my $ENV environment variables?

Dan Heller
http://www.danheller.com

Comment on Re^2: How to conditionally use CGI::Carp? Select or Download Code

Replies are listed 'Best First'.
Re^3: How to conditionally use CGI::Carp? by perrin (Chancellor) on May 06, 2005 at 20:47 UTC
I think the bottom line here is that CGI::Carp is kind of brittle and unreliable, and only works well for simple things. Using real exception handling, where you wrap your calls in eval {} and then catch the exceptions in your CGI script or command-line script and handle them appropriately, is the next level. There is more discussion of this here.	[reply]