Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Integer Size problem
Message-ID: <8379@hoptoad.uucp>
Date: 24 Aug 89 04:18:44 GMT
References: <15141@dartvax.Dartmouth.EDU> <11689@cit-vax.Caltech.Edu> <1465@draken.nada.kth.se> <17542@ut-emx.UUCP>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 14

In article <17542@ut-emx.UUCP> chrisj@emx.UUCP (Chris Johnson) writes:
>The Inside Macintosh X-Ref contains the most up-to-date list of routines
>that can move or purge memory that I know of.  In general, I'd say that you
>should check *every* routine you use against that table -- there are some 
>surprises there.  NumToString(), believe it or not, may move or purge memory,
>for instance.  Once again, use extreme caution.

Don't see why that should be surprising -- it's a package, after all, so
the system may do a resource fetch to get the code, which is stored in
a PACK resource.  All package routines may move or purge memory.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

A good flame strengthens its points; it does not stand in lieu of them.