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=-1.9 required=5.0 tests=BAYES_00,XPRIO autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e27871fabb6a1f9f,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-06-25 10:04:49 PST Path: archiver1.google.com!newsfeed.google.com!sn-xit-03!supernews.com!cyclone-sf.pbi.net!206.13.28.183!nnrp5-w.sbc.net.POSTED!not-for-mail From: "Ed Colbert" Newsgroups: comp.lang.ada Subject: Concurrency & I/O X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: Date: Mon, 25 Jun 2001 09:57:59 -0700 NNTP-Posting-Host: 63.193.36.170 X-Complaints-To: abuse@pacbell.net X-Trace: nnrp5-w.sbc.net 993488281 63.193.36.170 (Mon, 25 Jun 2001 09:58:01 PDT) NNTP-Posting-Date: Mon, 25 Jun 2001 09:58:01 PDT Organization: SBC Internet Services Xref: archiver1.google.com comp.lang.ada:9096 Date: 2001-06-25T09:57:59-07:00 List-Id: Hi All, Can someone confirm that it's still implementation defined whether I/O operations (Put, Get, 'Write, 'Read) are atomic, blocking, or subject to Priority_Ceiling. In quick review of the manual & rational, I found the following: 1) File_Type's and Root_Stream_Type are not publically defined using pragma Atomic. 2) Get_Immediate is non-blocking according Rationale section A.1. 3) A.10.7(24) Says Get_Immediate doesn't wait for end of line. 4) Annex H provides NO_IO pragma to disallow use of standard IO packages (and Ravenscare requires this pragma). 5) Annex D doesn't mention I/O. I don't see a specific statement about the semanics of I/O operations in a concurrent environment. Take Care, Ed