Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!ncar!midway!news
From: gft_robert@gsbacd.uchicago.edu
Newsgroups: comp.arch
Subject: Re: Macintosh OS
Message-ID: <1990Jun6.222126.2888@midway.uchicago.edu>
Date: 6 Jun 90 23:20:40 GMT
Sender: news@midway.uchicago.edu (News Administrator)
Organization: University of Chicago Graduate School of Business
Lines: 29

------- 
In article <:SY35CD@xds13.ferranti.com>, peter@ficc.ferranti.com (Peter da Silva) writes...

>How about the fact that programmers may have better things to do with their
>time than warp code to fit into the windowing universe? I realise that on
>the mac 90% of the programs are 90% user-interface, but that's not always
>the best way to do things. A compiler, for example, really has no business
>calling GetNextEvent *ever*.


And if the user wants to interrupt the compilation mid-compile?  You'd better
have some way of finding at least this out.  GetNextEvent (or WaitNextEvent)
seems the proper way to do this to me.

You may indeed have to change some of your code to run properly on the Mac.  Or
put another way: you may have to change some of your code to put the user in
complete control.  The above example as a case in point.

Robert





============================================================================
= gft_robert@gsbacd.uchicago.edu * generic disclaimer: * "It's more fun to =
=            		         * all my opinions are *  compute"         =
=                                * mine                *  -Kraftwerk       =
============================================================================