Re: ABORT = f(THROW)

I think what you are saying is that since SwiftX defines ABORT with THROW
and SwiftX words use ABORT and our app uses SwiftX words and because it is
difficult to insure that SwiftX (or our own) words that THROW are not used,
then we must CATCH for not only the top word but for every ACTIVATE of every
task.

Since SwiftX defines ABORT with THROW wouldn't it be safest for ACTIVATE to
do a CATCH DROP NOD by default? If we want to catch THROW then we can
ACTIVATE a nested CATCH -- better of both worlds.

-----Original Message-----
From: Elizabeth D. Rather [mailto:erather_at_forth.com]
Sent: Thursday, July 11, 2002 14:48
To: Bulgrien, Dennis; Swiftx Listserve
Subject: Re: [swiftx] ABORT = f(THROW)

If
you're
using THROW anywhere in your application, you should provide CATCHes
as appropriate. At minimum, you should have a CATCH at the very top
of your application, running the word that makes it all go.
----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe swiftx" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/swiftx -- check them out!
----------------------------------------------------------------------
THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.
Received on Fri Jul 12 2002 - 06:06:41 PDT