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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,4fe0da28a190b761 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!news3.google.com!news.germany.com!news.belwue.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Storage management Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <87fxmbog1u.fsf@mid.deneb.enyo.de> <87abciurrl.fsf@mid.deneb.enyo.de> <13hpf6ht4tl2m$.1su6rgr67eb2o$.dlg@40tude.net> <49140215$0$23600$4f793bc4@news.tdc.fi> <1pqpgcv6v4qxq$.1wkkgkw2yncf.dlg@40tude.net> <49142285$0$23584$4f793bc4@news.tdc.fi> <4914426e$0$30221$9b4e6d93@newsspool1.arcor-online.net> Date: Fri, 7 Nov 2008 15:41:39 +0100 Message-ID: <6unf81suhbzk$.7nbu89dhbtqp.dlg@40tude.net> NNTP-Posting-Date: 07 Nov 2008 15:41:39 CET NNTP-Posting-Host: ba211fd4.newsspool4.arcor-online.net X-Trace: DXC=HM;EC2ec?Jd:i=48;n?Z:`4IUKkgbI00KmO7gPda X-Complaints-To: usenet-abuse@arcor.de Xref: g2news2.google.com comp.lang.ada:8346 Date: 2008-11-07T15:41:39+01:00 List-Id: On Fri, 07 Nov 2008 14:28:14 +0100, Georg Bauhaus wrote: > Dmitry A. Kazakov schrieb: > >> There is no way Ada could abort I/O if the OS does not allow this. Second >> to Get_Line, or likely the first wanted case is canceling blocking socket >> read. I would give 98% that it never will work with ATC. > > OK, yet, does there have to be an operating system > that dictates how the Ada runtime does or does not > abort I/O? :-) Yes, an OO OS. If there were no I/O, but blocking entry calls, they would be trivially cancelable in a timed entry call. In the milliseconds area an I/O is not cancelable not because of physical reasons, like when the disk controller is busy positioning the heads. These take microseconds. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de