Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!apple!Apple.COM!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Macintosh handles
Message-ID: <2962@internal.Apple.COM>
Date: 21 Jul 89 20:12:18 GMT
Sender: usenet@Apple.COM
Distribution: comp.sys.mac.programmer
Organization: Objects-R-Us,  Apple Computer, Inc.
Lines: 22
References:<1044@clinet.FI> <8043@hoptoad.uucp>

In article <8043@hoptoad.uucp> tim@hoptoad.uucp (Tim Maroney) writes:
> The Tech Note used to have a note about a dynamic master pointer
> allocation technique used by ResEdit that was better, which was
> supposed to be the subject of a future Tech Note, but this comment is

I think the technique was to check the number of free master pointers in 
your main event loop and call MoreMasters there if the number was low.

This was important in 64K ROM days because code segments could be taking 
up space at the low end of the heap, where master pointer blocks are 
allocated.  This technique helps ensure that only the main segment was 
loaded at the time MoreMasters was called.

The 128K ROMs and beyond move code segments to the top of memory so that 
the low end of the heap is usually clear for nonrelocatable blocks.  (Note 
that the same technique would apply to allocating data for new windows.)

Larry Rosenstein, Apple Computer, Inc.
Object Specialist

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