Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C 4.0 questions
Message-ID: <10111@hoptoad.uucp>
Date: 7 Feb 90 21:09:33 GMT
References: <10682@bsu-cs.bsu.edu> <1968@cbnewsk.ATT.COM>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 18

From article <10682@bsu-cs.bsu.edu>, by mithomas@bsu-cs.bsu.edu
(Michael Thomas Niehaus):
>> 1.  If you declare an array in an object class definition, is it safe to
>>     use that array in a call to, say, an FSWrite routine?  I have created
>>     a 1K buffer and when it fills up I want to call FSWrite to write the
>>     whole chunk out.  Is this safe, or do I have to copy the whole array?
>>     (Or can I lock it down?)

In article <1968@cbnewsk.ATT.COM> ech@cbnewsk.ATT.COM (ned.horvath) writes:
>Lock the object: FSWrite can move memory, and TC4 objects are relocatable.

Why do you say FSWrite can move memory?  It's not in the lists, so unless
it's in an unlocked segment, I don't see how (or why!) it would move memory.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"I've been called an evil genius by cities of assholes...  but I know who
 these people are!  And they're on my list!" -- Robert Crumb