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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,39579ad87542da0e X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,UTF8 X-Received: by 10.180.75.133 with SMTP id c5mr2940076wiw.2.1369279394028; Wed, 22 May 2013 20:23:14 -0700 (PDT) Path: fw11ni1135wic.0!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.103.MISMATCH!feeder3.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.139.MISMATCH!xlned.com!feeder7.xlned.com!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!border4.nntp.ams.giganews.com!border2.nntp.ams.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!news.panservice.it!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Seeking for papers about tagged types vs access to subprograms Date: Wed, 15 May 2013 11:28:37 +0200 Organization: cbb software GmbH Message-ID: References: <12gn9wvv1gwfk.10ikfju4rzmnj.dlg@40tude.net> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: FbOMkhMtVLVmu7IwBnt1tw.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Date: 2013-05-15T11:28:37+02:00 List-Id: On Wed, 15 May 2013 06:24:49 +0200, Yannick Duchêne (Hibou57) wrote: > Le Tue, 14 May 2013 21:56:14 +0200, Robert A Duff > a écrit: >> Furthermore, lots of programs do NOT want that two-level structure. >> They just want a sequence of characters, with one (not two!) >> particular character that means "line break". They want to have >> code like: >> >> ... loop >> case Current_Char is >> ... > > That's a corner case, and why Ada should do pre‑tokenization for this > single case? It is not a tokenization. You turned abstraction upside down. The text file is a sequence of lines. A line is a sequence of characters. Period. If you have a broken OS, like Linux/Windows is, you cannot have this abstraction. Instead you emulate it as a lower-level stream of octets with escape sequences used to simulate lines. What is wrong with that? It conflates representation with the interface. > If end‑of‑line is made of two characters in some > environments, then the end of line token is not a character, or else it's > a character in a kind of internal character set (what most people surely > do, indeed, and that's out of the standard). It is not how it was under VMS. It did not have such stuff in record oriented files. Such files had each line kept with the character count. It was not a stream of characters. Though under VMS you could read it as a stream of octets if you wanted. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de