Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!cxt105
From: CXT105@psuvm.psu.edu (Christopher Tate)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C 4.0 questions
Message-ID: <90039.151841CXT105@PSUVM.BITNET>
Date: 8 Feb 90 20:18:41 GMT
References: <10682@bsu-cs.bsu.edu> <1968@cbnewsk.ATT.COM> <10111@hoptoad.uucp>
Organization: Penn State University
Lines: 25

In article <10111@hoptoad.uucp>, tim@hoptoad.uucp (Tim Maroney) says:

>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

According to Apple, the operating system has been patched from here to
hell and back again, and the lists are no longer valid.  A much safer
way to go is to assume that any trap routine can move memory, and set
things up to deal with this possibility.

Of course, this can be a real problem when you're trying to carefully
optimize things, or when you have to get down-and-dirty with the OS, but
it seems to me like a dandy way to ensure future compatibility....

-------
Christopher Tate                    |  "And as I watch the drops of rain
                                    |   Weave their weary paths and die,
cxt105@psuvm.psu.edu                |   I know that I am like the rain;
{...}!psuvax1!psuvm.bitnet!cxt105   |   There but for the grace of you go I."
cxt105@psuvm.bitnet                 |          -- Simon & Garfunkle