Path: utzoo!attcan!uunet!wuarchive!swbatl!texbell!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.arch Subject: Re: Macintosh OS Message-ID: Date: 7 Jun 90 14:54:06 GMT References: <1990Jun6.055847.14995@d.cs.okstate.edu> <:SY35CD@xds13.ferranti.com> <41684@apple.Apple.COM> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 20 In article <41684@apple.Apple.COM> daveo@Apple.COM (David M. O'Rourke) writes: > peter@ficc.ferranti.com (Peter da Silva) writes: > >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?? Then you hit ^C and abort that process. > 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. These are fine for initial coding and debugging, but that's a different animal from a production compiler. Also, it's generally more useful to fix a bunch of errors at once. You know: don't stop at one bug. -- `-_-' Peter da Silva. +1 713 274 5180. 'U` Have you hugged your wolf today? @FIN Dirty words: Zhghnyyl erphefvir vayvar shapgvbaf.