Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!think!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: LightSpeed C & Memory
Keywords: Multifinder, Lightspeed C, memory allocation
Message-ID: <2218@husc6.harvard.edu>
Date: 14 Jul 89 20:39:21 GMT
References: <2492@ur-cc.UUCP>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Distribution: usa
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 38

In article <2492@ur-cc.UUCP> giaccone@uhura.cc.rochester.edu (Tony Giaccone) writes:
>
>Mac II. However, I can only seem to get Lightspeed C to give me 384K.
>
>However, they don't seem to do much good. Is this because I'm running
>multi-finder? What do I have to do to twist Lightspeed to give me more
>memory? I've already selected the more memory option. Anybody have any
>idea on how I can get around this problem.

LightspeedC User's Manual, Chapter 7, Page 73:

	"THINKC uses the values you set in the Partition and MF Attrs
fields [of the Set Project Type dialog] to build the SIZE resource
your application needs to run under MultiFinder...

	...THINK C launches your application as if you had opened it
from the Finder. If you're using MultiFinder, your application runs
in its own partition."


LightspeedC User's Manual, Chapter 14, Page 174:

	"When this [the More Memory] option is on, THINK C tries to find
more memory DURING COMPILATION [caps are mine] by discarding certain
data structures."

		--Rich
~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

 I classify myself as a real developer because my desk is hip-deep in
 assembly-language listings and I spend more than 50% of my time in TMON.

~~~~~~~~~~~~~~~