Path: utzoo!utgpu!water!watmath!clyde!att!ihnp4!cbmvax!andy
From: andy@cbmvax.UUCP (Andy Finkel)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Who's got the lock?
Message-ID: <3796@cbmvax.UUCP>
Date: 17 May 88 17:29:24 GMT
References: <8805160340.AA23871@cory.Berkeley.EDU>
Reply-To: andy@cbmvax.UUCP (Andy Finkel)
Organization: Commodore Technology, West Chester, PA
Lines: 24

In article <8805160340.AA23871@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>:a "Lock" is an opaque structure that only the handler understands. These are
>
>	Actually, Locks are quite rigid.  The workbench guarantees that...
>that is, a bug in the workbench guarantees it.  You see, the workbench does
>a very bad thing to locks ... it copies them manually.  So the size of a 

Actually, only the first 6 fields are public.  The lock can be
longer.  (ram-handler and ffs have extended locks)
Workbench doesn't copy locks by hand...it copies (most of) the FileInfoBlock 
by hand. (Its the most of that gives us problems)

Never copy locks by hand.  Always use DupLock().

		andy
-- 
andy finkel		{ihnp4|seismo|allegra}!cbmvax!andy 
Commodore-Amiga, Inc.

"C combines the power of assembly language with the flexibility of
 assembly language."
		
Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.