Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!labrea!aurora!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpspdla!paulz
From: paulz@hpspdla.HP.COM (Paul Zander)
Newsgroups: comp.sys.amiga
Subject: Re: Transparent Asynchronous I/O.
Message-ID: <4160003@hpspdla.HP.COM>
Date: Thu, 27-Aug-87 20:55:07 EDT
Article-I.D.: hpspdla.4160003
Posted: Thu Aug 27 20:55:07 1987
Date-Received: Sun, 30-Aug-87 08:02:32 EDT
References: <514@sugar.UUCP>
Organization: HP Stanford Park - Palo Alto, Calif.
Lines: 9

Having once used a computer which buffers all I/O, I can
say that it can be a real pain in the a**.  The example
is still fresh in my mind of how the program had diagnostic
writes to isolate where it was crashing.  It would send the
write to the buffer, then proceed to the fatal error, leaving
some of the diagnostics still in the buffer!  
 
 I would agree that the best situation would be to have the
 operation selectable by the programmer.