Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!ucselx!sciences!purcell
From: purcell@sciences.tmc.edu (Guy B. Purcell)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Two suggestions for THINK C
Message-ID: <1990Aug1.220231.18581@ucselx.sdsu.edu>
Date: 1 Aug 90 22:02:31 GMT
References: <3758@crash.cts.com> <1990Jul31.224245.24110@agate.berkeley.edu>
Sender: news@ucselx.sdsu.edu (News Admin)
Organization: SDSU College of Sciences
Lines: 22

In article <1990Jul31.224245.24110@agate.berkeley.edu> lippin@math.berkeley.edu writes:
>Recently mdavis@pro-sol.cts.com (Morgan Davis) wrote:
>>In-Reply-To: message from eby@pegasus.ATT.COM
>>> 2) There ought to be a "Cancel" button on the compilation dialog.
>>Just press Command-Period to cancel a compilation.
>
>Some of us would *still* like a button, however.
>
>(While you're at it, how about making it a movable modal so we can
>switch out and do something else?)
>
>					--Tom Lippincott
>					  lippin@math.berkeley.edu
>
If this were done, compiling would be *much* slower.  Maybe later when
multitasking is handled better this will be worth it, but not currently.
I mean can you imagine putting in 'wait' statement in a compiler just
to allow other tasks some CPU time?  The OS should handle allocating
CPU resources, not the various applications.  Apple is working toward
this -- we just have to be patient.

Guy (purcell@zeus.sdsu.edu)