Path: utzoo!attcan!uunet!wuarchive!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!ucbvax!agate!eos!shelby!portia!Jessica!rick
From: rick@Jessica.stanford.edu (Rick Wong)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Integer Size problem
Message-ID: <4826@portia.Stanford.EDU>
Date: 25 Aug 89 02:18:04 GMT
References: <15141@dartvax.Dartmouth.EDU> <11689@cit-vax.Caltech.Edu> <1465@draken.nada.kth.se> <17542@ut-emx.UUCP> <28932@srcsip.UUCP>
Sender: USENET News System <news@Portia.stanford.edu>
Reply-To: rick@Jessica.UUCP (Rick Wong)
Organization: Stanford University
Lines: 18

In article <28932@srcsip.UUCP> mnkonar@src.honeywell.com (Murat N. Konar) writes:
>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
>
>Be very careful.  I have found that the list is not complete.  I found a 
>routine NOT listed that CAN move memory.  (FindWindow, I think.)      
>

Considering how scattered about this information is (volume 3, volume 5,
and the X-Ref), and how subject it is to change, it seems that such a
list would be a good subject for a tech-note.  Keith???

Of course, it's probably safest to assume the worst, that ANY trap or
procedure call can scramble the heap.

Rick Wong
rick@jessica.stanford.edu