Xref: utzoo comp.unix.internals:104 comp.unix.wizards:23768 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.unix.internals,comp.unix.wizards Subject: Re: UNIX semantics do permit full support for asynchronous I/O Message-ID: Date: 6 Sep 90 16:49:56 GMT References: <60345@lanl.gov> <27619@nuchat.UUCP> <1990Sep1.185221.8718@eng.umd.edu> <555@siswat.UUCP> <27813@nuchat.UUCP> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 18 In article <27813@nuchat.UUCP> steve@nuchat.UUCP (Steve Nuchia) writes: > An excellent point, one we would all do well to keep in mind. I would > have added to Lester's list of examples the event-driven style imposed > by modern user interface construction. ^^^^^^ Event loops are basically single loop control systems, such as are found in the simplest of embedded controllers: microwave ovens, for example. For them to have become synonymous with modern user interfaces borders on the obscene. The best way to implement a modern user interface is with multiple loops of control, such as Haitex' spreadsheet "Haicalc" on the commodore Amiga... Or, for a workstation environment, in NeWS. > AAAARRRRRRRGGGGHHHH!!!!! Sympathy. -- Peter da Silva. `-_-' +1 713 274 5180. 'U` peter@ferranti.com