Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!cunixf.cc.columbia.edu!cunixd.cc.columbia.edu!jtt
From: jtt@cunixd.cc.columbia.edu (James T. Tanis)
Newsgroups: comp.sys.mac.programmer
Subject: HLock interdiction??
Keywords: MacTutor, Memory Manager, DogCow
Message-ID: <1990Sep21.043054.24649@cunixf.cc.columbia.edu>
Date: 21 Sep 90 04:30:54 GMT
Sender: news@cunixf.cc.columbia.edu (The Daily News)
Reply-To: jtt@cunixd.cc.columbia.edu (James T. Tanis)
Organization: Columbia University
Lines: 10
Summary:Are H*ock still kosher?

while reading the September issue of MacTutor, in the Mousehole echo,
I saw a disturbing exchange...

the gist was, that HLock would _Unlock_ an object if it was locked to
begin with. Is this the case? Should I call HGetState first, to determine 
whether a handle is locked, and if so... with what mask???

For those interested, the exchange is on pg. 93 of the September issue.

thanks!