Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!shelby!polya!shap
From: shap@polya.Stanford.EDU (Jonathan S. Shapiro)
Newsgroups: comp.sys.mac.programmer
Subject: Re: System 7.0 Q & A
Message-ID: <9172@polya.Stanford.EDU>
Date: 14 May 89 00:37:54 GMT
References: <30353@apple.Apple.COM> <4666@okstate.UUCP> <1787@internal.Apple.COM> <7266@hoptoad.uucp> <13472@dartvax.Dartmouth.EDU>
Sender: Jonathan S. Shapiro <shap@polya.Stanford.EDU>
Reply-To: shap@polya.Stanford.EDU (Jonathan S. Shapiro)
Organization: Stanford University
Lines: 13

In article <13472@dartvax.Dartmouth.EDU> earleh@eleazar.dartmouth.edu (Earle R. Horton) writes:
>     Any Macintosh application written in a high-level language, using
>library glue derived from Apple's, and making calls to the Memory
>Manager will break when Apple makes low memory a protected area.  A
>side effect of using Apple glue to call a Memory Manager routine is to
>have the glue store a result code in the word at decimal 544.

Making page 0 shared whould largely solve the problem without
introducing significant incompatibilities.  One might even think about
making page 0 be a virtual page.


Jon