Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!decwrl!pa.dec.com!shodha.enet.dec.com!elvira!ridder From: ridder@elvira.enet.dec.com (Hans Ridder) Newsgroups: comp.sys.amiga.programmer Subject: Re: What's a Hanging Forbid!? Message-ID: <2423@shodha.enet.dec.com> Date: 31 Jan 91 14:44:51 GMT References: <1991Jan28.171326.6363@maytag.waterloo.edu> <2405@shodha.enet.dec.com> <18291@cbmvax.commodore.com> Sender: news@shodha.enet.dec.com Reply-To: ridder@elvira.UUCP (Hans Ridder) Organization: Digital Equipment Corporation, Customer Support Center Lines: 29 In article <18291@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes: >In article <2405@shodha.enet.dec.com> ridder@elvira.enet.dec.com (Hans Ridder) writes: >>What semaphore would you suggest I use to access the Exec Task list? > > A) You must Disable() to play with this list (and have a pretty damn > good reason for doing so!) Arghhh! What a fool am I! I realized this after I posted, but haven't been able to get back to news for a day or so. You see, I was just checking to see if anyone was paying attention.... (Won't work, huh?) > B) Exec (and it's lists) was written before there were > SignalSemaphores in the system, so it's stuck with locking methods > used in the initial implementation (usually Forbid()). Unfortunate > but unavoidable. Exactly! I was just trying to clarify the previous poster's general statement that semaphores should be used instead of Forbid()/Permit(). I wanted to point out that there's times when you have no choice, but I committed a technical gaffe in the process. Glad someone here is awake. Thanks Randell, for keeping the record straight! I'll go away now. >Randell Jesup, Keeper of AmigaDos, Commodore Engineering. -hans ------------------------------------------------------------------------ Hans-Gabriel Ridder Digital Equipment Corporation ridder@elvira.enet.dec.com Customer Support Center ...decwrl!elvira.enet!ridder Colorado Springs, CO