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.7 required=5.0 tests=BAYES_20,INVALID_DATE, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA Path: utzoo!watmath!clyde!cbosgd!ihnp4!ucbvax!mit-mc.arpa!KFL From: KFL@MIT-MC.ARPA (Keith F. Lynch) Newsgroups: net.lang.ada Subject: Re: text_io considered error prone? Message-ID: <[MIT-MC.ARPA].642077.850911.KFL> Date: Wed, 11-Sep-85 21:17:18 EDT Article-I.D.: <[MIT-MC.ARPA].642077.850911.KFL> Posted: Wed Sep 11 21:17:18 1985 Date-Received: Fri, 13-Sep-85 03:20:56 EDT Sender: daemon@ucbvax.ARPA Organization: The ARPA Internet List-Id: Date: Tue 10 Sep 85 22:34:22-EDT From: "Art Evans" As I read Chapter 14, Bakin's challange is unfair. In 14.3(6) and (7), there is a careful definition of what Ada means by "text file". TEXT_IO provides for I/O from such a file, and for nothing else. The last sentence of (7) says The effect of input or output of control characters (other than horizontal tabulation) is not defined by the language. Thus it's not surprising that copying an arbitrary string of ASCII characters is beyond the capabilities of TEXT_IO. I think that what 14.3.7 means is that the effect on the output device is not defined. For instance some control character may make the output device go into graphics mode, and that would not be a violation of the Ada specs. The context can be judged by 2.1, which defines the Ada character set as consisting of the letters, numerals, several special symbols, space bar, and the control characters HT, VT, CR, LF, and FF. These characters all have meaning to Ada. All other Ascii characters are merely arbitrary bit patterns as far as Ada is concerned. It does NOT follow from that that Ada is unable to copy a file containing such characters. ...Keith