The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Line Terminators in Text Files [
Date: Mon, 4 Sep 2017 14:34:18 -0400	[thread overview]
Message-ID: <CAC20D2NEc+V9mb2HJwtC_dmNJY61=0mgDdrnk=O=DOANMBJrGw@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VS8TNJSStmgSyT9xifbqtbsWQqN_0XaPss2oVwJn3B=8Q@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

On Mon, Sep 4, 2017 at 1:29 PM, Paul Winalski <paul.winalski at gmail.com>
wrote:

> I was once a firm believer in the virtues of a record-oriented I/O
> interface such as RMS, but after using UNIX and Linux for several
> years I became a convert to stream I/O as the base primitive.  One can
> always implement record I/O on top of stream I/O if you want it, but
> it's difficult to do it the other way round.

​Amen - this was my point with Dave​.

One thing, I'll grant him though from the VAX-11/C experiment which I was
wrong at the time.  In those days, I hated that he had ignored Dennis'
'register' keyword.  As a programmer and thinking in terms of C being a
better assembler, I liked being able to control the compiler.   But in my
years of eating lunch you and the other folks in the compiler group I
admit, I admit you have won me over.   You guys can do a better job than I
can, particularly with random architectures.    If code is to be portable,
then let the compiler to the register assignment.

Dave was right about about that one, but maybe we shouldn't tell me him one
of the old UNIX guys I said that.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170904/c9a73106/attachment.html>


  reply	other threads:[~2017-09-04 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-03 20:06 Clem Cole
2017-09-03 21:42 ` Warner Losh
2017-09-04 17:29 ` Paul Winalski
2017-09-04 18:34   ` Clem Cole [this message]
2017-09-04 20:28     ` ron minnich
2017-10-01 17:24   ` Tom Ivar Helbekkmo

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='CAC20D2NEc+V9mb2HJwtC_dmNJY61=0mgDdrnk=O=DOANMBJrGw@mail.gmail.com' \
    --to=clemc@ccc.com \
    /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).