🚀 go-pugleaf

In article <13231@ncoast.UUCP> jamiep@ncoast.UUCP (Jamie Purdon) writes:
>*The* place to begin scanning the screen structs is at
>  IntuitionBase->FirstScreen
> 
>Unless you're simply checking if you're the "upfront" screen,
>you should probably forbid/permit around any "screen structure walking".
> 
>(finishing DIGIpaint2....;-)

	If you're working on DigiPaintII, then you should be aware that
using Forbid/Permit is not *neccesarily* the correct way to inspect public
system structures.  I noticed GrabANIM doing the same thing with
IntuitionBase, and a big bell went off in my head (JimM's words can be
pretty infectious, you know...).

	The correct way to look at IntuitionBase is to first call
LockIBase().  This keeps Intuition from fooling with IntuitionBase while
you're looking at it.  You may think Forbid() does this, but if Intuition
just happens to be in the middle of a modification when it gets switched
out in time for you to say Forbid(), then IntuitionBase is in an
inconsistent state, and you could get propelled into The Twilight Zone.

	The Exec memory free list is arbitrated with Forbid/Permit (isn't
it?).  IntuitionBase is arbitrated with LockIBase/UnlockIBase().  If you
don't use the right locking mechanism, your program will lose one day.

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	INET: well!ewhac@ucbvax.Berkeley.EDU
 \_ -_		Recumbent Bikes:	UUCP: pacbell > !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor