Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!think!barmar
From: barmar@think.uucp (Barry Margolin)
Newsgroups: comp.sys.mac
Subject: Re: UNIX and Mac applications on the Mac II
Message-ID: <4124@think.UUCP>
Date: Tue, 28-Apr-87 14:46:42 EDT
Article-I.D.: think.4124
Posted: Tue Apr 28 14:46:42 1987
Date-Received: Thu, 30-Apr-87 02:11:50 EDT
References: <9519@duke.cs.duke.edu> <252@rocky.STANFORD.EDU>
Sender: news@think.UUCP
Reply-To: barmar@godot.think.com.UUCP (Barry Margolin)
Distribution: world
Organization: Thinking Machines Corporation, Cambridge, MA
Lines: 10
Keywords: UNIX, Mac II, multitasking, windows

In article <252@rocky.STANFORD.EDU> ali@rocky.UUCP (Ali Ozer) writes:
>But most Mac applications are use busy-waiting in their main event loops,
>no? It might be possible to run them as tasks, but they will all 
>be "cpu-hogs". It seems like most old applications will not do too well
>under a multitasking Mac II Finder.

Each time through the loop a Mac application is required to call
getevent (I think that's its name, I haven't actually done any Mac
programming).  This can make a system call so that the Mac-emulation
process will block until there's actually an event.