Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Semaphores.
Message-ID: <8711012250.AA16257@cory.Berkeley.EDU>
Date: Sun, 1-Nov-87 17:50:57 EST
Article-I.D.: cory.8711012250.AA16257
Posted: Sun Nov  1 17:50:57 1987
Date-Received: Thu, 5-Nov-87 21:07:03 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 20

>Whether Forbid/Permit or ObtainSemaphore/ReleaseSemaphore (which is
>LockIBase() amounts to) are used to arbitrate shared data between

	Speaking of which, the documentation on the new Semaphore calls
is seriously lacking.  It amounts to something like:

	ObtainSemaphore(): This function obtains a semaphore.

	Right... That really tells me how to use the function.  How about 
some better docs on these functions??  I must have added two hundred lines to
my autodocs since I got them.... every time I figure out how an inadequately
explained function works, I add it to my manual set.  The EXEC IO system is
the worst of the lot.

	I can finally understand some of the original RKM stuff... I realized
that the author was talking about what the ROM routines need to do, not what
the original program or destination device driver needs to do.  Great..
Lovely, just what I didn't need to know.

					-Matt