Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-modula-2
From: nagler@ORB.UUCP (Rob Nagler)
Newsgroups: net.lang.mod2
Subject: re: exception handling
Message-ID: <8602281650.AA00613@orb.sun.uucp>
Date: Fri, 28-Feb-86 11:50:39 EST
Article-I.D.: orb.8602281650.AA00613
Posted: Fri Feb 28 11:50:39 1986
Date-Received: Sat, 1-Mar-86 18:11:05 EST
Sender: uucp@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21


	exception signalling
I believe that this answers a different question.  I think of it
more as an inter-module communication mechanism versus an exceptional
condition handler.  For example, one might use such a mechanism 
for notifying a module of an asynchronous event occuring (the mouse
entering a window is an example). 

           fault inhibiting
Tough to do and then once you've inhibited the fault, how (who) do
you notify the about to fail process?  It tends to lead to very
messy code  as well.

           scope of fault handlers
More of the same....

	interaction with processes
Certainly faults are on a per process basis.  An interesting
question to ask is: can you force faults on other processes?

Rob