Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!apple!Apple.COM!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Application Unexpectedly Quits
Message-ID: <4766@internal.Apple.COM>
Date: 16 Oct 89 16:57:17 GMT
Sender: usenet@Apple.COM
Organization: Objects-R-Us,  Apple Computer, Inc.
Lines: 24
References:<5174@lindy.Stanford.EDU> <35672@apple.Apple.COM>

In article <35672@apple.Apple.COM> keith@Apple.COM (Keith Rollin) writes:
> It does this with a two forked technique. First of all, it determines 
how much
> memory your program will ever need to hold all System and CODE resources 
at the
> time or maximum use. It goes and totes up the sizes of all the CDEF, 
WDEF, 

Actually, you have to configure this number in a resource.  MacApp does 
provide tools to help determine the maximum code usage of the program.  
Assuming that you tell MacApp the maximum, then it will ensure that the 
maximum is always available.

The technique of ensuring that a 32K block is always available will work, 
provided any particular operation requires that only one extra code 
segment be loaded.  Otherwise, you might have enough to load 1 segment but 
not the second.


Larry Rosenstein, Apple Computer, Inc.
Object Specialist

Internet: lsr@Apple.com   UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1