🚀 go-pugleaf

In article <255@husc6.HARVARD.EDU> hadeishi@husc4.UUCP (mitsuharu hadeishi) writes:
>
>Mac software architecture, although revolutionary in its time, makes
>it MUCH more difficult for old applications to run comfortably in a
>multitasking environment (and much less efficient, since an event loop
>is inherently less efficient than a event-driven task (that uses
>task Wait()ing.))

Not so.  Most Mac applications that don't do things that Apple says not
to do should have no trouble in a multitasking environment.  The main
problems with multitasking on the Mac are in the OS, not the applications.
MultiMac showed that most Mac applications can deal with multitasking.

Also, I don't think that a polled event loop has to be "much less" efficient.
When there is no event for the process, GetNextEvent will just return a
null event.  The process would most likely then just call GetNextEvent
again.  This is less efficient, but not by much.


-- 
What's the difference between a duck?

Tim Smith       USENET: sdcrdcf!ism780c!tim   Compuserve: 72257,3706
		Delphi or GEnie: mnementh