Path: utzoo!attcan!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!zaphod.mps.ohio-state.edu!rpi!bu.edu!dartvax!eleazar.dartmouth.edu!llama
From: llama@eleazar.dartmouth.edu (Joe Francis)
Newsgroups: comp.sys.mac.programmer
Subject: Re: C++/MacApp questions
Keywords: spam spam MPW in the background spam spam spam
Message-ID: <24751@dartvax.Dartmouth.EDU>
Date: 27 Sep 90 22:49:30 GMT
References: <10594@pt.cs.cmu.edu>
Sender: news@dartvax.Dartmouth.EDU
Organization: Dartmouth College, Hanover, NH
Lines: 17

In article <10594@pt.cs.cmu.edu> mkb@rover.ri.cmu.edu (Mike Blackwell) writes:

>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?

Actually, you CAN compile in the background.  I'm am while I write this
note (and while I read yours).  Perhaps you mean you want to be able to 
continue to use MPW while it's compiling, to edit source, etc.?  Picky,
picky....

Seriously though, I second Mike's request for MPW to retain some functionality
during compiles.  With the ammount of memory CFront eats, though, I realize
that I wouldn't really be able to take advantage of this without virtual
memory.  Any plans for (post system 7.0) MPW 3.x to allow this?

Cheers, Joe