From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucio De Re To: 9fans@cse.psu.edu Subject: Re: [9fans] libbio and CR-LF Message-ID: <20030224170906.X15898@cackle.proxima.alt.za> References: <6d3220b4.0302221754.17fc79a@posting.google.com> <325d51a3bce898a06f32d76ea420f62b@plan9.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <325d51a3bce898a06f32d76ea420f62b@plan9.bell-labs.com>; from Russ Cox on Mon, Feb 24, 2003 at 09:49:22AM -0500 Date: Mon, 24 Feb 2003 17:09:06 +0200 Topicbox-Message-UUID: 7042d724-eacb-11e9-9e20-41e7f4b1d025 On Mon, Feb 24, 2003 at 09:49:22AM -0500, Russ Cox wrote: > > If the CR is there it should be reported. > Libbio should not do any funny conversions > like Windows stdio libraries traditionally have. > They confuse more than they help. > Isn't the CP/M approach that when reading a "text" file, one treats the combination as end of line, where the is optional (I seem to recall some software that used them in the reverse sequence, mechanical typewriter-style)? In other words, one can treat the as optional if it immediately precedes for "text" files. In fact, any number of s can be discarded in such a situation. s standing alone must either be translated or treated as themselves. Whatever is decided, it must be cast in stone, of course. That is, if a "text" mode can be specified. ++L