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 autolearn=ham
	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.226.10 with SMTP id ro10mr11526697pbc.6.1328545650186;
        Mon, 06 Feb 2012 08:27:30 -0800 (PST)
Path: 
 lh20ni267370pbb.0!nntp.google.com!news2.google.com!postnews.google.com!f14g2000yqe.googlegroups.com!not-for-mail
From: Adam Beneschan <adam@irvine.com>
Newsgroups: comp.lang.ada
Subject: Re: GNAT: no more exception raised on illformed text file?
Date: Mon, 6 Feb 2012 08:27:29 -0800 (PST)
Organization: http://groups.google.com
Message-ID: 
 <a30e14f5-d403-43c1-8eea-ae5fab3bf7c2@f14g2000yqe.googlegroups.com>
References: <op.v88wsspwule2fv@douda-yannick> <jgorsc$ho9$1@dont-email.me>
NNTP-Posting-Host: 66.126.103.122
Mime-Version: 1.0
X-Trace: posting.google.com 1328545650 18292 127.0.0.1 (6 Feb 2012 16:27:30
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 6 Feb 2012 16:27:30 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: f14g2000yqe.googlegroups.com; posting-host=66.126.103.122;
 posting-account=duW0ogkAAABjRdnxgLGXDfna0Gc6XqmQ
User-Agent: G2/1.0
X-Google-Web-Client: true
X-Google-Header-Order: ARLUEHNKC
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64;
 Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR
 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30618; .NET4.0C),gzip(gfe)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: 2012-02-06T08:27:29-08:00
List-Id: <comp.lang.ada>

On Feb 6, 7:33 am, "J-P. Rosen" <ro...@adalog.fr> wrote:
> Le 06/02/2012 08:08, Yannick Duch=EAne (Hibou57) a =E9crit :
>
> > 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.
>
> > Is this on purpose?
>
> I don't know, but it is definitely acceptable, and many would view this
> as an improvement.

Right--in fact, we've had issues where a customer created a file with
Notepad and didn't hit RETURN at the end of the last line, and then
asked why a program wasn't reading the last line of the file.  This
sort of behavior can be surprising and unwelcome.

                           -- Adam