Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!amdahl!rtech!beaver!sbrooks From: sbrooks@beaver..UUCP (Steve Brooks) Newsgroups: comp.arch Subject: Re: Macintosh OS Message-ID: <5424@rtech.Ingres.COM> Date: 7 Jun 90 20:37:42 GMT References: <1990Jun6.055847.14995@d.cs.okstate.edu> <:SY35CD@xds13.ferranti.com> <41684@apple.Apple.COM> Sender: news@rtech.Ingres.COM Reply-To: sbrooks@ingres.com (Steve Brooks) Organization: Ingres Corporation. Lines: 28 In article <41684@apple.Apple.COM> daveo@Apple.COM (David M. O'Rourke) writes: >peter@ficc.ferranti.com (Peter da Silva) writes: >>the best way to do things. A compiler, for example, really has no business >>calling GetNextEvent *ever*. > > What if the user, a programmer in this case, wants to stop the compile?? > That's the responsibility of the operating system. This is exactly my biggest complaint about the Macintosh environment. There is no clear distinction between applications and operating system functions. The definition of an operating system is the set of software components which provide allocation of system resources. Allocation is provided to application programs. There should always be a clear distinction between OS and application. Enough of this, lets get back to comp.arch. >-- >daveo@apple.com David M. O'Rourke ===== SjB. My opinions.