Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.sys.mac.programmer
Subject: Re: HLock Function List
Message-ID: <3954@uakari.primate.wisc.edu>
Date: 21 Feb 91 01:10:14 GMT
References: <49376@apple.Apple.COM>
Sender: bin@primate.wisc.edu
Reply-To: bin@primate.wisc.edu
Lines: 20

From article <49376@apple.Apple.COM>, by keith@Apple.COM (Keith Rollin):
> 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.

No, I don't have a specific example.  I was thinking of the caution in
the list in IM-V, for example, which says that many more routines move
now than previously.  I grant you that that doesn't say specifically that
any *old* routines move memory now that didn't before, but it sounds
pretty ominous to me.  If Apple wants to come out and say: these routines
don't move memory, *and they nevery will*, find.  Until then, I'll stick
by my statement that it's safest to assume that any ToolBox routine
might.

Is that over-cautious, or simply prudent?

--
Paul DuBois
dubois@primate.wisc.edu