You should use the functions 'try and 'disarm. After disarming and error you
can continue to operate in most cases.
if error? error-open-port: try [open port][error-open-port: disarm
error-open-port]
I hope that helps. Also you may want to check out the errors chapter of the
Core.pdf appendix B pages B3-B5.
Paul Tretter
----- Original Message -----
From: "CRS - Psy Sel/SPO, COUSSEMENT Christophe, CPN"
<[EMAIL PROTECTED]>
To: "REBOL List (E-mail)" <[EMAIL PROTECTED]>
Sent: Wednesday, January 24, 2001 7:50 AM
Subject: [REBOL] A way to intercept REBOL/Command crash
> Hi REBOLians,
>
> I need bady a solution to the following problem:
>
> For the system I made, which is transaction-intensive, the REBOL
file-server
> crashes under particuliar conditions.
> In order to prevent it I would like to find a generic solution to
intercept
> the exception which causes the crash, so the processes could go further
> after a exception report.
>
> Does anybody know any use of catch/throw-on-error which placed on a
> strategic place in the script could help me out of this ?
> Can throw-on-error prevent a process to be killed by an -unidentified-
> exception ?
>
> Because the crash conditions have not already been clearly identified, I'm
> not yet in state of giving more details about it.
>
> Best Regards,
>
> chr==
>
>
> --
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the
> subject, without the quotes.
>
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
