Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!gatech!udel!new
From: new@udel.EDU (Darren New)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Forbid() is not nice
Message-ID: <15582@louie.udel.EDU>
Date: 16 May 89 16:25:07 GMT
References: <17148@usc.edu> <24279@agate.BERKELEY.EDU> <18268@cup.portal.com> <17183@usc.edu> <21814@srcsip.UUCP> <5847@cs.Buffalo.EDU> <9160@polya.Stanford.EDU> <207@doctor.Tymnet.COM>
Sender: usenet@udel.EDU
Reply-To: new@udel.EDU (Darren New)
Organization: University of Delaware
Lines: 11

In article <207@doctor.Tymnet.COM> jms@doctor.Tymnet.COM (Joe Smith) writes:
>Most of the time, a program using Forbid really doesn't need to stop all
>scheduling.  That's like using a sledge hammer as a fly swatter.  We really

You can just boost the priority of your task temporarily.
Using Forbid() is needed if any task could screw you up, like while
you are walking the free memory lists (since any task could AllocMem
and change pointer out from under you). If you only wish to
keep a particular task from running while you are, push your
pripority up or even better push the priority of the other task
down.   -- Darren