9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] libbio and CR-LF
Date: Mon, 24 Feb 2003 10:14:34 -0500	[thread overview]
Message-ID: <2c43986586d52f0b4b3b1878469ddbcb@plan9.bell-labs.com> (raw)
In-Reply-To: <20030224170906.X15898@cackle.proxima.alt.za>

> Isn't the CP/M approach that when reading a "text" file, one treats
> the <CR><LF> combination as end of line, where the <CR> 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 <CR> as optional if it immediately
> precedes <LF> for "text" files.  In fact, any number of <CR>s can be
> discarded in such a situation.  <CR>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.

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.



  reply	other threads:[~2003-02-24 15:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 10:00 Saroj Mahapatra
2003-02-24 10:54 ` [9fans] " Douglas A. Gwyn
2003-02-24 14:49 ` [9fans] " Russ Cox
2003-02-24 15:09   ` Lucio De Re
2003-02-24 15:14     ` Russ Cox [this message]
2003-02-24 15:27       ` Boyd Roberts
2003-02-24 15:29       ` Lucio De Re
2003-02-24 21:54 ` [9fans] CRLFication (was: libbio and CR-LF) Geoff Collyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2c43986586d52f0b4b3b1878469ddbcb@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).