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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.36.116.1 with SMTP id o1mr1224207itc.12.1493235166531; Wed, 26 Apr 2017 12:32:46 -0700 (PDT) X-Received: by 10.157.46.178 with SMTP id w47mr35779ota.12.1493235166505; Wed, 26 Apr 2017 12:32:46 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!news.glorb.com!c26no1720894itd.0!news-out.google.com!x200ni2016itb.0!nntp.google.com!c26no1720891itd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 26 Apr 2017 12:32:44 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2600:1011:b117:ef95:ae2b:bf36:4494:eeaf; posting-account=O1bJfwoAAAC_Vd4l-lauVJNDJxmhacGI NNTP-Posting-Host: 2600:1011:b117:ef95:ae2b:bf36:4494:eeaf References: <1896933e-e985-420b-a4fe-9cca76af9976@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Weird Bug in Get_Line From: Brian Kolden Injection-Date: Wed, 26 Apr 2017 19:32:46 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:46636 Date: 2017-04-26T12:32:44-07:00 List-Id: =20 > According to the ARM (A.10), Text_IO operates on "text files" as defined = there.=20 > Part of that definition is that "the end of a line is marked by a _line= =20 > terminator_" and "the end of a file is marked by the combination of a lin= e=20 > terminator immediately followed by a page terminator and then a _file=20 > terminator_" [A.10(7)]. So technically, an implementation of Text_IO is n= ot=20 > required to work on files that aren't valid Text_IO text files, and the e= rror is=20 > that your file is not a valid Text_IO text file. >=20 > However, such an implementation of Text_IO is pretty useless on most syst= ems,=20 > and compiler writers usually try hard to make sure that Text_IO works on = foreign=20 > files. That's fair, however, the functionality of Text_IO is currently inconsisten= t. I feel that it should either be reworked to always throw the exception o= r not. At the moment, it comes across as a logical error since it will only= complain at a few, very specific line lengths.