Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!gatech!ncsuvx!lll-winken!lll-lcc!well!ewhac
From: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Newsgroups: comp.sys.amiga
Subject: Re: Re: Recognizing the break character
Message-ID: <6664@well.UUCP>
Date: 30 Jul 88 06:36:40 GMT
References: <3498@louie.udel.EDU> <2674@amiga.UUCP>
Reply-To: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Organization: onhigh!oracle
Lines: 29
Quote: "This sounds like a horrible TV movie starring Mr. T and Bert Convy."

In article <2674@amiga.UUCP> neil@spam.UUCP (Neil Katin) writes:
:First of all, the EXEC exception handler is fully general.  You
:can longjmp out of it to previous call frames, just as in UNIX.
:Indeed, the whole idea of Amiga execeptions was to allow unix-like
:signal processing.
:
:We implemented it (back in V21, if memory serves).  We tested it.
:We loved it.  We used it.  We crashed with it.
:
:The problem is a fundamental one in the amiga's design.  Short of
:redesigning the task model, EXCEPTIONS ARE LIMITED IN USE TO ONLY
:VERY CONSTRAINED CONDITIONS, which almost never exist in normal
:use.  [ ... ]
:
:	Neil Katin
:	(the person guilty of adding exceptions to exec...)

	Don't feel guilty; exceptions are great.  I've used them in the
aforementioned constrained conditions, and they work very nicely.

	Matt Dillon made their use even more attractive when he created
'qint', which is a form of Forbid()/Permit() for exception signals only.  As
long as the task manages its interrupts correctly, they can be just as
useful as the UNIX equivalent (albeit more trouble to use).

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	INET: well!ewhac@ucbvax.Berkeley.EDU
 \_ -_		Recumbent Bikes:	UUCP: pacbell > !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor