wyant@APOLLO.UUCP (Geoffrey Wyant) (02/27/86)
At one point I thought that the case could be made for putting some sort of exception
handling facility into modula-2. After going home and mulling over it a bit for a while,
I realized that a "90%" solution could be effected outside of the langauge. What I'd like to
start seeing now is a consensus on what a good exception handling library should contain; e.g.
exception signalling (call declared exception handlers)
stack unwinding (unix style setjmp & longjmp)
fault inhibiting
scope of fault handlers
interaction with processes (i.e. are fault handlers/stack unwinders global or process local).
How about other peoples thoughts on these ?
Geoff Wyant
-------nagler@ORB.UUCP (Rob Nagler) (02/28/86)
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