Mark A. Fuller [EMAIL PROTECTED] wrote on 10/08/2006 02:24:57
PM:
Oh yeah. :) I've seen that before but it didn't register with me. I
just looked at the source for C::A and realize it wraps eval around
the execution of the run mode. So, doing what I suggested (put an
eval around the run
Yesterday I revisited CGI::Prototype. (Regained my conclusion that I don't know
why it was created.). One thing stood out to me. After the stub starts the
process (by executing $self-activate which is equivalent to C::A's $self-run)
a mainline of method calls to the application's code
On Sun, 8 Oct 2006, Mark A. Fuller wrote:
The idea of die'ing anywhere in my application seems elegant to
me. Right now I have to do my own $template processing anywhere an
unexpected/unrecoverable error occurs (to display a common page).
Have you looked at error_mode()? I think it offers
From: Sam Tregar [EMAIL PROTECTED]
Have you looked at error_mode()? I think it offers exactly what
you're looking for,
Oh yeah. :) I've seen that before but it didn't register with me. I just looked
at the source for C::A and realize it wraps eval around the execution of the
run mode. So,
On Sun, 8 Oct 2006 11:55:28 -0400 (EDT), Mark A. Fuller wrote:
Hi Mark
eval {
$webapp-run();
};
$webapp-error($@) if $@;# failed something, go to safe mode
Besides Sam's explanation, surely you see that after your app has died, the
speed of the eval is irrelevant, right :-)?
--
Cheers
