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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,ccd337934e964b6a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII
Received: by 10.68.213.68 with SMTP id nq4mr11872143pbc.2.1328555052636;
        Mon, 06 Feb 2012 11:04:12 -0800 (PST)
Path: 
 lh20ni267759pbb.0!nntp.google.com!news2.google.com!postnews.google.com!18g2000yqe.googlegroups.com!not-for-mail
From: Shark8 <onewingedshark@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: GNAT: no more exception raised on illformed text file?
Date: Mon, 6 Feb 2012 11:04:12 -0800 (PST)
Organization: http://groups.google.com
Message-ID: <8801c492-52d4-47be-a976-06f10de5c1df@18g2000yqe.googlegroups.com>
References: <op.v88wsspwule2fv@douda-yannick>
NNTP-Posting-Host: 24.230.151.194
Mime-Version: 1.0
X-Trace: posting.google.com 1328555052 17995 127.0.0.1 (6 Feb 2012 19:04:12
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 6 Feb 2012 19:04:12 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: 18g2000yqe.googlegroups.com; posting-host=24.230.151.194;
 posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: HUALESNKRC
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 6.1;
 rv:9.0.1) Gecko/20100101 Firefox/9.0.1,gzip(gfe)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2012-02-06T11:04:12-08:00
List-Id: <comp.lang.ada>

On Feb 6, 1:08 am, Yannick Duch=EAne (Hibou57)
<yannick_duch...@yahoo.fr> wrote:
> Hi all,
>
> Seems my FSF GNAT (*) does not raise an exception anymore when
> encountering the last line of a malformed text file; that is, a text file
> whose last line is not terminated with an end-of-line.

Such a file is NOT a malformed text-file; that definition is a UNIX-
ism and therefore applicable ONLY to the UNIX/LINUX world. In Windows,
for example, a user in Notepad (or wordpad, or any other editor) can
save a text-file without such a termination (as Adam points out) and
it IS a valid text-file precisely because Windows does not define a
text-file in that manner. (IIRC all that Windows needs is the ASCII
EOF character.)