Re: Error messages in Apache::Registry

On 17 Sep 2002 at 13:27, Perrin Harkins wrote: > Matt wrote some stuff for the guide explaining why the die handler is not > the best approach. Basically, it means all errors will be treated the > same. Ahh, right. Is this what you're referring to?

Re: Error messages in Apache::Registry

William McKee wrote: >>The way that most people would recommend in A::R or anything else is to >>trap errors with eval blocks and then handle them appropriately. > > I thought I was doing that at a global level by throwing an error with > die() that was caught by CGI::Carp. I'm realizing that it

Re: Error messages in Apache::Registry

On 16 Sep 2002 at 18:10, Perrin Harkins wrote: > The way that most people would recommend in A::R or anything else is to > trap errors with eval blocks and then handle them appropriately. I thought I was doing that at a global level by throwing an error with die() that was caught by CGI::Carp. I

Error messages in Apache::Registry

Hi folks, I'm a new user to mod_perl. I'm using Apache::Registry to run some scripts that have been written using the CGI::Application framework. Previously, under mod_cgi, I've been using the CGI::Carp set_message method of capturing a die and returning a customized error message to the scree