🚀 go-pugleaf

In article <418hv3$451@steel.interlog.com>,
Dave Glue <daveacg@interlog.com> wrote:
>Matthew Kramer <kram1968@gmi.edu> wrote:
>
>>On Sun, 20 Aug 1995, Dave Glue wrote:
>
>>> Since 3.0.  And unlike the Mac, most Windows applications were
>>> co-operative aware 4-5 years ago.
>
>>No, Windows has never multi-tasked.  IT's task-swapped, yes, but never 
>>multi-tasked.
>
>Please read  a book on occasion to get your terms straight.
>
>Windows multitasks.  Has since 3.0.  So does the Mac.  The ability to
>perform two tasks at the same time is multitasking.

But these systems can't do that. If I write a loop that doesn't
explicitly call a yield routine, only my task will execute. There is
no hint of concurrency in that at all, since each program has to invoke
another with an explicit call.  Multitasking means that you at least
simulate concurrency using time slicing. It means that other tasks are
truly running whether or not my program yields. It means that I
can send signals and messages to that program from another program.

Coroutines should be excluded from the definition of multitasking proper.


-- 
Finger c2a192@keats.ugrad.cs.ubc.ca for PGP public key. Or contact
one of the public key servers -- the key id is 0xD3C7995D.