Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think!mintaka!bloom-beacon!ftp!poopsie!bootsie!olson
From: olson@bootsie.UUCP (Eric Olson)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C 4.0 project problems...
Message-ID: <7@bootsie.UUCP>
Date: 11 Jan 90 22:08:26 GMT
References: <69286@tiger.oxy.edu>
Reply-To: olson@bootsie.UUCP (Eric Olson)
Organization: Lexington Software Design, Lexington, MA
Lines: 24

In article <69286@tiger.oxy.edu> sonenbli@oxy.edu (Andrew D. Sonenblick) writes:
>
>and try to rerun it, it compiles and then Think C reports out of memory errork

I am not sure about what I am about to say, except to say that it works for me.
I don't know which things cause Think C's "Out of Memory" alert and which would
cause some other memory error (i.e., I don't know which of these things will
actually fix your problem-- try 'em all [in order]).

1. Change the application's partition size in the "Set Project Type" dialog.
2. Select "More Memory" in the "Edit" menu "Options..." dialog "Preferences"
   section.  This slows down compiling and I don't know if it helps in your
   case, since I thought it was for temporary data.
2. Make Think C's partition size _smaller_, since it isn't all being used
   and maybe it's the application partition that can't be allocated.
3. Don't run the debugger, or decrease its partition size (I wouldn't make
   it smaller than the minimum though-- its tiny anyway).

I have successfully compiled huge TCL things [Prepare()] on a 2.5 Meg Plus.
By huge I mean that the Project file is about 1.3 Meg.

-Eric
-- 
Eric K. Olson            olson@endor.harvard.edu          harvard!endor!olson