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,fb00b4031f5d9d4a
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: GNAT's Text_IO & empty files
Date: 1998/07/07
Message-ID: <dewar.899850671@merv>#1/1
X-Deja-AN: 369387698
References: <35A0B7C5.1011D794@Maths.UniNe.CH> <dewar.899765885@merv>
 <35A21B66.1509490B@cl.cam.ac.uk>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 899850759 24808 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-07-07T00:00:00+00:00
List-Id: <comp.lang.ada>

Markus says

<<Having just read RM A.10 M-'7, I think the Ada standard is badly
  formulated here. It is not clear how a file or a page with zero
  lines or a file with zero pages has to be encoded. The standard writes
  that a file is a sequence of pages and a page is a sequence of lines,
  but it does not handle the obvious border case of zero-length
  sequences adequatly. It would have been better to write just that
  every line terminates with a line terminator, and every page
  terminates with a page terminator, and then everything would have
  been clear and consistent. With a bit good will, the Ada RM language
  can even be interpreted that way.>>


I disagree. The RM deliberately stays out of the business of describing
how a file is encoded, and that is as it should be, since the appropriate
encoding is most certainly system dependent. It just describes a set of
high level features, and you can implement them anyway you want. People
often assume for instance that the codes in a Text_IO file will match
those of Standard.Character, but nowhere in the RM is there such a
requirement, and a compiler that always used Unicode for Text_IO files
is perfectly well conforming!