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,5afe598156615c8b X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!204.71.34.3!newsfeed.cwix.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Get_Line problem (GNAT bug?) Date: 7 Dec 2006 22:04:14 -0600 Organization: LJK Software Message-ID: References: <1c1gbc5u9cpvp.1wj1zhhn7q86j$.dlg@40tude.net> <1tua3ke1kfoog.1wqou5d9mwtly.dlg@40tude.net> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1165550578 1579 192.135.80.34 (8 Dec 2006 04:02:58 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Fri, 8 Dec 2006 04:02:58 +0000 (UTC) Xref: g2news2.google.com comp.lang.ada:7862 Date: 2006-12-07T22:04:14-06:00 List-Id: In article , Robert A Duff writes: > I think the Unix idea -- "line terminator (or separator?) = a particular > character" -- is a pretty convenient model. It's certainly convenient > for parsing input text: read one char at a time, and deal with it, > treating end-of-line as one possible case. E.g., an Ada compiler > typically works that way. It constrains the ASCII values that can be in a record. That may not be important for compilers but I write programs where record boundaries different from "new line" is quite useful in the output files. > To represent end-of-line as TWO characters is just plain stupid. I will raise (lower) your TWO characters and say that inline record boundaries are foolish.