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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,39479d7149884fb6 X-Google-Attributes: gid103376,public From: Gautier Subject: Re: Philosophical Question (End_Of_File) Date: 2000/02/11 Message-ID: <38A494C3.659F9193@maths.unine.ch>#1/1 X-Deja-AN: 584721983 Content-Transfer-Encoding: 7bit References: <38A4799B.6D2E7ABE@ftw.rsc.raytheon.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Trace: 11 Feb 2000 23:00:02 +0100, mac13-32.unine.ch MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-02-11T00:00:00+00:00 List-Id: Wes Groleau wrote: (...) > So why do some vendors implement End_Of_File something like this? > function End_Of_File (....) is > begin > Read_Without_Advancing; > return False; > exception > when End_Of_File => return True; > end End_Of_File; Mmmmmh interesting... BTW GNAT that doesn't do so (in Direct_IO, 3.11) is *much* faster with simple loop within a begin..exception..end block than with "while not End_Of_File loop" (maybe because both End_Of_File and Read do check file status ?) ex. @ http://members.xoom.com/_XMCM/gdemont/uza_html/unz_io__adb.htm#9_11 G.