Re: #0:handle_uncaught_error()

• Date: Wed, 14 Feb 1996 23:09:12 PST
• From:
  bmgustav@bioinformatics.weizmann.ac.il (Gustavo Glusman)
• Content-Type: text/plain; charset="us-ascii"

Pavel asked:
>> The question is, what's the general rule for which object to call when an
>> arbitrary MOO task raises an uncaught error?

Phantom answered:
>I guess the general rule for which object would
>handle it would be which object's connection would be the one to see the
>traceback.  If a timeout traceback would be sent to a connection coming
>through
>#123, then #123 would be the object to handle that traceback.

Um, isn't this exactly 'player' ?
As the player:confunc() call was moved to $user_disconnected(), and there's
no trouble making the latter call the former, why not just code
$handle_task_timeout() to do some relevant perms check, and then pass it on
to player:handle_task_timeout() ?

OTOH, if player is an invalid objnum, it would make sense to call
:handle_task_timeout() on the object through which this in/outbound
connection is passing (which I think was the original issue of this
thread).

-------------------------------------------------------------
Gustavo Glusman               Founder/administrator of BioMOO
-- Gustavo@bioinformatics.weizmann.ac.il
-- http://bioinformatics.weizmann.ac.il/Gustavo
-- BioMOO: telnet bioinformatics.weizmann.ac.il 8888
           WWW:   http://bioinfo.weizmann.ac.il/BioMOO

• Prev: Re: #0:handle_uncaught_error()
• Next: Re: #0:handle_uncaught_error()
• Index: MOO-cows
• Thread: MOO-cows