Newsgroups: comp.sys.amiga.advocacy
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!snorkelwacker.mit.edu!stanford.edu!neon.Stanford.EDU!torrie
From: torrie@cs.stanford.edu (Evan Torrie)
Subject: Re: 680x0 vs 80x86
Message-ID: <1991Jun25.062028.2265@neon.Stanford.EDU>
Sender: torrie@neon.Stanford.EDU (Evan James Torrie)
Organization: Computer Science Department, Stanford University, Ca , USA
References: <92@ryptyde.UUCP> <4671.tnews@templar.actrix.gen.nz> 	<105@ryptyde.UUCP> <vhHfw1=@cs.psu.edu> <1991Jun24.051233.3203@neon.Stanford.EDU> <mykes.3740@amiga0.SF-Bay.ORG>
Date: Tue, 25 Jun 1991 06:20:28 GMT
Lines: 23

mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes:

>Too bad MPW doesn't multitask.  

  This is more a multi-threading, rather than multitasking example, since
the MPW editor and compiler run in the same address space.  I guess you 
can argue semantics of multi-threading vs multitasking.

>When you start up a compile in MPW, you can't
>use your MPW editor to browse your files.  This was a horrible design decision
>when they made MPW in the first place.  Since multifinder isn't a true multitasking
>solution, the best you can hope for is to run two HUGE copies of MPW and maybe
>the MPW tools will be friendly enough to allow you to compile from one and edit
>from the other.

  Or else, you use a different editor to edit your programs...  like
Alpha, the Emacs clone.  

-- 
------------------------------------------------------------------------------
Evan Torrie.  Stanford University, Class of 199?       torrie@cs.stanford.edu  
"And in the death, as the last few corpses lay rotting in the slimy
 thoroughfare, the shutters lifted in inches, high on Poacher's Hill..."
