Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!apple.com!gandalf
From: gandalf@apple.com (Martin Gannholm)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: HyperCard application memry requirements.
Message-ID: <11910@goofy.Apple.COM>
Date: 30 Jan 91 00:36:07 GMT
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 28
References:<8540@pbhyf.PacBell.COM> <1991Jan30.095551.2855@waikato.ac.nz>

In article <1991Jan30.095551.2855@waikato.ac.nz> ldo@waikato.ac.nz 
(Lawrence D'Oliveiro, Waikato University) writes:
> In article <8540@pbhyf.PacBell.COM>, mtchris@PacBell.COM
> (Mitchell T. Christensen) hits a refrain familiar to all us long-time
> MultiFinder users: why should we have to keep reconfiguring our
> application partition sizes?
> 
> The solution is simple: when running under MultiFinder, HyperCard
> should allocate the widely-variable parts of its memory usage in
> the system heap.

Aaaargh! Sorry, no can do. There are enough things that use the system 
heap but shouldn't. The solution under System 7.0 is to use MultiFinder 
temp memory to hold document-specific information. HyperCard 2.0 even uses 
temp memory if it is available, but before 7.0 the support for temp memory 
isn't flexible enough to use it for a wider range of things. In 6.0.x 
systems you should only use MF temp memory (that's temp as in "temporary") 
for a very short time.

Soon enough, this cold winter will be over, system 7 will ship, companies 
will rev their apps & everything will be, as we say in Swedish, "en dans 
p} rosor" (like dancing on roses).

Martin Gannholm
Apple Computer

Exclaimer!!!   I never said it...Nobody heard me say it...You can't prove 
anything!