Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!fwi.uva.nl!mel!freek
From: freek@fwi.uva.nl (Freek Wiedijk)
Newsgroups: comp.sys.mac.programmer
Subject: Re: HLock
Message-ID: <292@fwi.uva.nl>
Date: 17 Dec 89 12:35:07 GMT
References: <3331@hub.UUCP> <3332@hub.UUCP>
Sender: news@fwi.uva.nl
Reply-To: freek@fwi.uva.nl (Freek Wiedijk)
Organization: Faculteit Wiskunde & Informatica, Universiteit van Amsterdam
Lines: 12

In article <3332@hub.UUCP> 6600pete@hub.UUCP writes:
>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. The list, in other words, is no longer valid.

You mean that nowadays even BlockMove moves memory? :-)

I would think that if I patch a trap that may NOT move memory, and that
patch moves memory, then that patch has a bug!
--
Freek "the Pistol Major" Wiedijk                  Path: uunet!fwi.uva.nl!freek
#P:+/ = #+/P?*+/ = i<<*+/P?*+/ = +/i<<**P?*+/ = +/(i<<*P?)*+/ = +/+/(i<<*P?)**