Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!bu.edu!mirror!howtek!cory
From: cory@howtek.UUCP (Cory Kempf)
Newsgroups: comp.sys.mac.programmer
Subject: Re: C++/MacApp questions
Summary: RTFM
Keywords: spam spam MPW in the background spam spam spam
Message-ID: <1541@howtek.UUCP>
Date: 3 Oct 90 15:36:29 GMT
References: <10594@pt.cs.cmu.edu> <24751@dartvax.Dartmouth.EDU>
Reply-To: cory@howtek.UUCP (Cory Kempf)
Organization: Howtek Inc., Hudson, NH
Lines: 24

In article <24751@dartvax.Dartmouth.EDU> llama@eleazar.dartmouth.edu (Joe Francis) writes:
>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?

You can.

>			      Perhaps you mean you want to be able to 
>continue to use MPW while it's compiling, to edit source, etc.?  Picky,
>picky....

Actually, you can do this also.  In the docs that came with my copy of
MPW 3.1, there were explicit directions for how to do this.  They involve
making a second copy of the MPW Shell and start up files in a second
directory.  The second copy can be used to edit, etc, while the first is
compiling.  Not the most elegant solution though.

Personally, I would prefer to see some form of Job Control (cf csh(1))
implimented.  The impression that I got was "not in my lifetime" (actually,
to be fair, there are some problems that need to be worked out first)

+C