Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!agate!ragu.berkeley.edu!lippin
From: lippin@ragu.berkeley.edu (The Apathist)
Newsgroups: comp.sys.mac.programmer
Subject: Re: creating resources
Message-ID: <1991Mar22.025750.17269@agate.berkeley.edu>
Date: 22 Mar 91 02:57:50 GMT
References: <1065@ub.d.umn.edu> <1991Mar21.234809.26603@ux1.cso.uiuc.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: lippin@math.berkeley.edu
Organization: Authorized Service, Incorporated
Lines: 23

Recently resnick@cogsci.uiuc.edu (Pete Resnick) wrote:

> You *really* don't want to create a resource with thousands of
> integers anyway. There is a Tech Note on why not to abuse the Resource
> Manager in just this way.

This won't cause a problem.  What the Resource Manager objects to is
creating thousands of resources.  Creating a single large resource
will slow down updates a bit, but won't really bother it.  (Early
versions of the Resource Manager had problems with resources bigger
than 32K, but that's long gone.)

Also, the scale of this problem may not be that big: ten thousand integers
(assuming the Pascal integer type) is less than 20K.  If it gets up
around fifty thousand, one might want to look at putting them in the
data fork, where one can read them in pieces and not keep the whole
table in memory at once.

					--Tom Lippincott
					  lippin@math.berkeley.edu

	"The living dead don't need to solve word problems!"
					--Calvin