[Catalyst] "or die" replacement?

[apv]

I personally believe the do or die (or croak or whatever) approach
is the best. I have come to utterly despise software that pretends
it's working when the action requested failed somewhere in some
measure.

My main cat project is dying with codes right now, e.g., "RC_503:
Database cannot be reached," if there is a \bDBI\b in the
$c->error(s) and sending email to the dev (via a config file
address) with the Email plugin.

Bad software that is painful to the user can go without being
fixed. Bad software that is painful to the developer tends to get
action pretty quickly.

-Ashley

On Wednesday, March 15, 2006, at 06:04  AM, Andreas Jellinghaus wrote:

> Hi,
>
> so far I wrote my code with max. error checking and
> simply inserted "or die" after almost everything I
> do.
>
> but "or die" is nice while developing, in the final
> application I should used something more userfriendy.
>
> What are your recommendations, how should I replace
> my "or die" code? It is important to me to give
> some feedback to the user that something went wrong,
> and - to be sure - create a proper entry in some
> log file, e.g. apache error log (catalyst running
> with mod_perl inside apache).
>
> Regards, Andreas
>
> _______________________________________________
> Catalyst mailing list
> Catalyst at lists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst
>
>