Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!snorkelwacker!tut.cis.ohio-state.edu!ucbvax!pasteur!helios.ee.lbl.gov!ucsd!hub!6600pete
From: 6600pete@hub.UUCP
Newsgroups: comp.sys.mac.programmer
Subject: Re: HLock
Message-ID: <3373@hub.UUCP>
Date: 20 Dec 89 00:04:04 GMT
References: <1989Dec19.091303.13316@agate.berkeley.edu>
Sender: news@hub.UUCP
Lines: 21

From article <1989Dec19.091303.13316@agate.berkeley.edu>, by lippin@skippy.berkeley.edu (The Apathist):
>>DTS' official position now is that there are so many patched traps running
>>around calling the Memory Manager that you need to lock and unlock handles
>>around ANY trap call.

> Seriously, if this were DTS's position...

I've seen it twice now posted by DTS employees with no disclaimers
attached. With explicit declarations that it was official dogma,
no less. (No, I don't log these things to disk.)

I know it sounds ugly, but that's what's been said.

Perhaps it IS the case that one should never write into an unlocked
hanlde by any means. (Note: I said PERHAPS.)

Additional input from DTS would be helpful, I'm sure.
-------------------------------------------------------------------------------
Pete Gontier   | InterNet: 6600pete@ucsbuxa.ucsb.edu, BitNet: 6600pete@ucsbuxa
Editor, Macker | Online Macintosh Programming Journal; mail for subscription
Hire this kid  | Mac, DOS, C, Pascal, asm, excellent communication skills