Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!mips!apple!bbn!bbn.com!levin
From: levin@bbn.com (Joel B Levin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: FSWrite moving memory? (was Re: Think C 4.0 questions)
Message-ID: <52320@bbn.COM>
Date: 16 Feb 90 15:47:03 GMT
References: <10193@hoptoad.uucp> <2032@cbnewsk.ATT.COM> <1990Feb13.173605.7633@intercon.com> <10268@hoptoad.uucp>
Sender: news@bbn.COM
Reply-To: levin@BBN.COM (Joel B Levin)
Organization: BBN Communications Corporation
Lines: 19

In article <10268@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
|...not sure where the FS gets the access path buffer from, but note that
!if it were being gotten from the memory manager, PBClose would also be
|on the list because the buffer would be deallocated then. . . .

     and
|(Actually, given that closing a desk accessory or driver can release
|memory, I don't know why PBClose isn't on the list.  Ideas?)

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.

	/JBL (probably full of beans)
=
Nets: levin@bbn.com  |  "There were sweetheart roses on Yancey Wilmerding's
 or {...}!bbn!levin  |  bureau that morning.  Wide-eyed and distraught, she
POTS: (617)873-3463  |  stood with all her faculties rooted to the floor."