Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!daveo From: daveo@Apple.COM (David M. O'Rourke) Newsgroups: comp.arch Subject: Re: Macintosh OS Message-ID: <41684@apple.Apple.COM> Date: 6 Jun 90 22:19:15 GMT References: <1990Jun6.055847.14995@d.cs.okstate.edu> <:SY35CD@xds13.ferranti.com> Organization: Apple Computer Inc, Cupertino, CA Lines: 25 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?? Even though a compiler may be primarily a batch oriented process, there is still a user which needs to be serviced. In addition more complex compiler designs of the future might call for more programmer interaction when it finds a syntax error, allowing the programmer to fix the syntax error and continue. I basically agree with your point, but I think you're limiting your view of what a compiler should be to what compilers current are, there are reason's and examples for user interaction in almost any well thoughtout software tool. But that's just my $0.02 worth... :-) -- daveo@apple.com David M. O'Rourke "Hey where'd you learn to shoot like that?" ... "At the 7-11." -- Marty McFly (Back to the future III) _______________________________________________________________________________ I do not speak for Apple in any official sense.