Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpda!hpsal2!hpcupt1!hpindda!grant From: grant@hpindda.HP.COM (Grant Haidinyak) Newsgroups: comp.sys.amiga Subject: Re: Spawning tasks which draw . . . Message-ID: <6570008@hpindda.HP.COM> Date: 9 Dec 87 21:18:56 GMT References: <787@rocky.STANFORD.EDU> Organization: Hewlett Packard, Cupertino Lines: 18 >Even better: why don't you and your task use semaphores or signals >to let the parent task know when it can remove the child task. The reason you would want an OS supported way of setting a critical region it is that what if there is no explicit syncronization between the parent and the child (i.e. exec), then how do you abort the task/process. The scenario that I am talking about is: Joe Helpless User executes a program, for some reason, the program goes into a tight loop, Joe then types a control-c (or what ever), and the program is stopped, and ALL of the resources that it had allocated would be freed. Wouldn't it be nice.... Hey, if unix can do it why cann't we!! >-- Peter da Silva `-_-' ...!hoptoad!academ!uhnix1!sugar!peter Grant