Path: utzoo!utgpu!water!watmath!clyde!rutgers!cbmvax!bpa!burdvax!udel!gatech!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Killing a task using SetExcept()
Keywords: tasking, signals, exception processing
Message-ID: <44623@sun.uucp>
Date: 8 Mar 88 17:24:02 GMT
References: <7409@agate.BERKELEY.EDU> <1401@louie.udel.EDU> <1406@louie.udel.EDU>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 15

In article <1406@louie.udel.EDU> schifala@udel.EDU (Jim Schifalacqua) writes:
>Hello,
>   I am trying to design a neat way to kill tasks spawned by my programs.
>I want to use exception processing via SetExcept and the tc_ExceptCode field.

If I may suggest an alternative? It is generally not nice to kill tasks 
forcibly on the Amiga. It leads to all sorts of race conditions, vis-a-vis
freeing resources, stopping I/O, etc. A much cleaner solution is to give
your task a message port that it monitors. When you want it to die, send
it a kill message. It would then clean up and reply. After the reply you
could RemTask(), it. 

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.