Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!mtxinu!taniwha!paul
From: paul@taniwha.UUCP (Paul Campbell)
Newsgroups: comp.sys.mac.programmer
Subject: Re: FSWrite moving memory? (was Re: Think C 4.0 questions)
Message-ID: <504@taniwha.UUCP>
Date: 19 Feb 90 07:24:56 GMT
References: <10193@hoptoad.uucp> <2032@cbnewsk.ATT.COM> <1990Feb13.173605.7633@intercon.com> <10268@hoptoad.uucp> <52320@bbn.COM> <10302@hoptoad.uucp>
Reply-To: paul@taniwha.UUCP (Paul Campbell)
Organization: Taniwha Systems Design, Oakland
Lines: 21

In article <10302@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>In article <52320@bbn.COM> levin@BBN.COM (Joel B Levin) writes:
>>I don't have my Inside Mac and Technotes etc. here, but it seems to me
>>that RELEASING memory would not result in MOVING memory; I thought
>>this could only happen when something needs memory and there is not a
>>big enough piece available.
>
>No, I checked this before writing the above, and DisposPtr and DisposHandle
>are on the move/purge memory routine list.

I always thought that they weren't just worried about moving memory but
about doing things in the memory manager which were not locked (for example
they are halfway through updating some memory manager data structure when 
an interrupt comes along that delivers your completion routine, you dispose
your handle and trash the half updated structure).

	Paul
-- 
Paul Campbell    UUCP: ..!mtxinu!taniwha!paul     AppleLink: CAMPBELL.P
You know there's something wrong when 100,000 people marching in Moscow
make page 1 and 400,000 in Washington don't .....