Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!paperboy!think.com!spool.mu.edu!sol.ctr.columbia.edu!samsung!uunet!mcsun!ukc!edcastle!cs.ed.ac.uk!cs.edinburgh.ac.uk!nick From: nick@cs.edinburgh.ac.uk (Nick Rothwell) Newsgroups: comp.sys.mac.programmer Subject: Re: HLock Function List Message-ID: <6484@skye.cs.ed.ac.uk> Date: 20 Feb 91 12:57:01 GMT References: <1991Feb20.042807.12553@ux1.cso.uiuc.edu> Sender: nnews@cs.ed.ac.uk Reply-To: nick@lfcs.ed.ac.uk Organization: Tasha Yar Appreciation Soc... oh, sh*t Lines: 20 In article <1991Feb20.042807.12553@ux1.cso.uiuc.edu>, dmmg1176@uxa.cso.uiuc.edu (David M Marcovitz) writes: > 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. I'm not sure the list is that useful, especially when you start running INITs which patch otherwise memory-safe traps. My approach: assume that *any* trap can move memory (well, except BlockMove, which I use to copy stuff between handles and the like). Patch BlockMove and I'll kill you... -- Nick Rothwell, Laboratory for Foundations of Computer Science, Edinburgh. nick@lfcs.ed.ac.uk !mcsun!ukc!lfcs!nick ~~ ~~ ~~ ~~ Captain Waldorf has analogue filters. You do not. ~~ ~~ ~~ ~~ ~~ ~~ ~~ ~~ Do not try to imitate them or any of their actions. ~~ ~~ ~~ ~~