From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,INVALID_DATE, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,18385551e0d37b37 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-10-31 04:46:47 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!EU.net!uunet!newsflash.concordia.ca!nstn.ns.ca!nstn.ns.ca!nntp-user From: Newsgroups: comp.lang.ada Subject: Re: Ada replacements for DOS I/O Date: 31 Oct 1994 08:46:27 -0400 Organization: Nova Scotia Technology Network Sender: news@nstn.ns.ca Message-ID: <45420.cwarwick@fox.nstn.ns.ca> Reply-To: NNTP-Posting-Host: owl.nstn.ns.ca X-Minuet-Version: Minuet1.0_Beta_14.1 X-POPMail-Charset: English Date: 1994-10-31T08:46:27-04:00 List-Id: On 27 Oct 1994 19:04:50 -0400, Robert Dewar wrote: >The failure to do concurrent I/O is certainly not a bug (nothing in the >Ada standard requires, or even implies, that I/O done from one task is >concurrent with the execution of other tasks). No, but it does require a higher priority task take precedence over a lower. With the Alsys DOS product all task processing regardless of priority ceases. I think the nature of Ada tasking is such that I/O be at least interruptable when a higher priority task becomes ready to run. >If you need concurrent I/O, put an operating system on your PC (many >choices including OS/2, NT, Solaris, SCO Unix, Linux, BSD386, Lynx, >Nextstep), and then shop for a compiler that definitely supports the >concurrency that you need. The most logical step is of course to write the IO functions we need in Ada (or find someone who already has, hence the start of this thread) and then the bug goes away, regardless of operating system... >You burned yourself on this one by making a totally unwarranted assumption! I don't think its unwarrwanted. Alsys provided use with all the OS tools we needed to implement this project, which included interrupt handling, multiple tasking, and IO to nonstandard cards. I don't think given all this it was unreasonable to assume they had thought about the interaction between tasks and DOS. -- Lorne Elliot in a Conan the Barabarian suit, or "Beware the fool, for only the fool may speak the truth" Chris Warwick cwarwick@fox.nstn.ns.ca warwick@anchor.hfx.prior.ca