In general I tend to be in the camp of wanting modules I use to return error indicators to my code rather than dying noisily. The more it can tell me "hey, you screwed up" without taking down the entire script, the better. I'm _not_ a fan of modules who use Carp and the like internally, as they often overwrite SIGWARN and SIGDIE handlers I use in my own code, which is annoying and counter-productive.
-Stephen -----Original Message----- From: Mark Stosberg [mailto:[EMAIL PROTECTED]] Sent: Sunday, December 30, 2001 11:14 AM To: Greg Marr Cc: CGI::App list Subject: Re: [cgiapp] proposal for enhancement: error handling for load_tmpl()and other failures On Sun, 30 Dec 2001, Greg Marr wrote: > > I was just working with CGI::App today and ran into a situation I've > > run into several times before: I got an internal server error because > a > > template could not be found when load_tmpl() was called. It would be > > nice if CGI::App could systematically address this issue by providing > > some error handling for this case. > > use CGI::Carp qw(fatalsToBrowser); Thanks Greg. I suppose in the case where I want to see the errors in development, but not in production, this could be a fine solution. (which is most of what I want, personally). For production use, this has the drawback of not supporting templates as well, but it would still get the job done. -mark http://mark.stosberg.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
