Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ucla-cs!cc1
From: cc1@CS.UCLA.EDU
Newsgroups: comp.sys.amiga
Subject: Re: Transparent Asynchronous I/O.
Message-ID: <7887@shemp.UCLA.EDU>
Date: Wed, 26-Aug-87 17:44:45 EDT
Article-I.D.: shemp.7887
Posted: Wed Aug 26 17:44:45 1987
Date-Received: Fri, 28-Aug-87 07:23:18 EDT
References: <514@sugar.UUCP>
Sender: root@CS.UCLA.EDU
Reply-To: cc1@CS.UCLA.EDU (Michael Gersten)
Organization: Ucla Computer Club (disclaimer)
Lines: 13
Keywords: UNIX AmigaDOS

In article <514@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>Why doesn't AmigaDOS support transparent asynchronous writes? If you're
>example) a short debugging message to a CON: device, and that window has it's
>layers locked (say, you hit the spacebar), why should you have to wait for

Please, make it an option, preferably switchable. Being able to stop a program
by hitting space is a great feature right now. Besides, how do you ever handle
I/O errors when you don't know what write caused it? (Even unix has this
problem).

			Michael
   The opinions represented here are a result of being educated at a
school that discriminates againts roosters. Only the birds are responsible.