Path: utzoo!attcan!uunet!husc6!mailrus!cwjcc!hal!nic.MR.NET!umn-cs!berlin!grg
From: grg@berlin.acss.umn.edu (George Gonzalez)
Newsgroups: comp.sys.mac.programmer
Subject: Re: FullWrite Professional -- Six Years Later
Summary: Not Apple's fault
Keywords: frustration really about OS
Message-ID: <258@berlin.acss.umn.edu>
Date: 16 Nov 88 15:17:23 GMT
References: <17069@agate.BERKELEY.EDU>
Organization: U of M MicroGroup, Minneapolis
Lines: 12


The reason that Mac applications can't be moved once started isn't Apple's
fault.  It's because all applications depend on absolute addressing.  Once
an application has started up, its stack will be full of absolute addresses:
return addresses from procedure calls, dynamic links to vars in other procs,
VAr parameter addresses, pointers (absolute).  All these addresses are
pure machine addresses.  The application, its stack, and its heap *can't*
be moved because of all these references into the code, stack and heap.

  I don't know anything about the Amiga.  But I'd like to know how they
could move a running application.  I suspect they can't either, and have
similar memory fragmentation problems.