Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!keith
From: keith@Apple.COM (Keith Rollin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: HLock Function List
Message-ID: <49376@apple.Apple.COM>
Date: 20 Feb 91 19:01:27 GMT
References: <1991Feb20.042807.12553@ux1.cso.uiuc.edu> <3947@uakari.primate.wisc.edu>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 28

In article <3947@uakari.primate.wisc.edu> bin@primate.wisc.edu writes:
>From article <1991Feb20.042807.12553@ux1.cso.uiuc.edu>, by dmmg1176@uxa.cso.uiuc.edu (David M Marcovitz):
>> 
>> I vaguely remember seeing a reference to a list of functions that
>> cause blocks of memory to be relocated.  That is, I will need to call
>> HLock before (and HUnlock) after these functions to keep certain
>> blocks from being relocated.  Can someone please tell me where I can
>> find this list.  Thanks.
>
>It's safest to consider the list to be "all ToolBox calls", because
>although not every call *today* has the potential to cause memory to
>be moved, the list continues to expand over time.  A function that's
>safe today might not be safe tomorrow.

Do you have any examples of this? I know that the System SW guys are
pretty careful, for example, to not turn SetRect into a call that moves
or purges memory. This should also be true for all other calls that are
not listed as moving memory.

By the way, David, the lists you are looking for are in the back of
Inside Macintosh.

-- 
------------------------------------------------------------------------------
Keith Rollin  ---  Apple Computer, Inc.  ---  Developer Technical Support
INTERNET: keith@apple.com
    UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith
"Argue for your Apple, and sure enough, it's yours" - Keith Rollin, Contusions