Re: crash_message

new topic     » goto parent     » topic index » view thread      » older message » newer message

----- Original Message -----
From: Boehme, Gabriel <gboehme at POBOXB1.HQ.MSMAIL.MUSICLAND.COM>
To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
Sent: Tuesday, August 31, 1999 1:46 PM
Subject: Re: crash_message


> David Cuny wrote:
>
> >I'd like to see a crash_routine variable, so I can set up something
> >like this:
> >
> >   crash_routine = routine_id("myRecoveryRoutine")
>
> But what happens if your recovery routine has an error and causes a crash?
> smile
>
> Just thought I'd point it out, because I used to get myself in a *TON* of
> trouble in Basic, doing this kind of thing with buggy "on error" routines.

If your error routines are single-pass, like starting at one end of a
daisychain and each error ripple-passes to the other end, there is no
problem with loopy errors like that. The last error handler could be the
non-replaceable non-preemptable standard Eu error handler, it would simply
report the most recent error it is handed, even if it occurs in a preceeding
user-written error handler.

Kat

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu