On Sat, 24 Dec 2005, Mark Stosberg <[EMAIL PROTECTED]> wrote:
You should get the 500 error for compile time issues, but the
DebugScreen for run time issues. That part works for me.
I know, but it's definitely giving the default 500 error page both
run-time as well as of course compile-time errors.
CGI::Carp::DebugScreen works fine in the same application if used in
place of CAP::DebugScreen. Hope it's not just me.
It's not. There's not a whole lot benefit of the CAP integrated version
anyway, besides that it integrates with ViewCode. It's a nice feature,
but doesn't sound like it is worth these other problems.
I was actually test-driving this one to see how it compares with the
error handler I usually use - CGI::HTMLError, which I think I still
prefer, especially as I have a version patched to work under Apache
handler & Apache registry.
--
Richard Jones
Leeds, UK
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
