Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!fluke!kurt
From: kurt@tc.fluke.COM (Kurt Guntheroth)
Newsgroups: comp.sys.amiga
Subject: Re: Transparent Asynchronous I/O.
Message-ID: <1675@sputnik.COM>
Date: Sun, 6-Sep-87 12:57:10 EDT
Article-I.D.: sputnik.1675
Posted: Sun Sep  6 12:57:10 1987
Date-Received: Sun, 6-Sep-87 21:15:57 EDT
References: <514@sugar.UUCP> <4160003@hpspdla.HP.COM>
Sender: news@tc.fluke.COM
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Lines: 9

If the program doesn't wait for the I/O to finish

1.  Don't you loose one good place for a context swithc, and therefore have
    a weaker multitasking?

2.  How do you know an I/O operation has failed?  You don't get a return
    code since you didn't wait for the I/O to finish.  You would get some
    asynchronous interrupt saying "I/O operation failed on some port some
    time in the past."  Diagnosis will be a major pain.