Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!uunet!unisoft!hoptoad!farcomp!murat
From: murat@farcomp.UUCP (Murat Konar)
Newsgroups: comp.sys.mac.programmer
Subject: Re: C++/MacApp questions
Message-ID: <242@farcomp.UUCP>
Date: 30 Sep 90 01:36:26 GMT
References: <10594@pt.cs.cmu.edu>
Reply-To: murat@farcomp.UUCP (Murat Konar)
Organization: Farallon Computing Inc. Berkeley, CA
Lines: 29

In article <10594@pt.cs.cmu.edu> mkb@rover.ri.cmu.edu (Mike Blackwell) writes:
[on using C++ and MacApp under MPW]
>Is there ANY way to speed things along besides turning on the RAM disk
>cache? It looks like most of the time is spent in CFront processing all
>those .h files. Will the dump/load mechanism work here, and if so, can you
>give me a quick tutorial?

We are using fx's and IIx's with 50 mHz accelerators and still run out of
stuff to read.  I think that I'd probably be a lot more productive if we
were using THINK Pascal and MacApp on a ci instead of C++ on an fx.  There
is a bright side, though.  I have learned how to juggle during compiles.  
You can too!

( I don't want to start any flame fests over the relative merits of C++
and Object Pascal.  It's just that the THINK environments are so much
faster than MPW, and THINK C just doesn't support MacApp).

>Why oh why can't I compile in the background? I have gobs of real memory,
>and I'd even spring for another disk for swap space. Sigh. Will Sys7 solve
>this?

We have no problems compiling in the background with 8 megs (except 
occasionally the compile or link will fail because it can't get enough memory).

-- 
____________________________________________________________________
Have a day. :^|             
Murat N. Konar	
murat@farcomp.UUCP             -or-          farcomp!murat@apple.com