From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Line Terminators in Text Files [
Date: Sun, 3 Sep 2017 15:42:24 -0600 [thread overview]
Message-ID: <CANCZdfpD7yQp0ZHo6HcZQSch=K-RXTf8sXiELU8MtZ_ZbDb1eg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MbSa3YxkkKdYUj01R0C-cnm0Bv6d+dAsBtEhHCegL4Qw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]
On Sun, Sep 3, 2017 at 2:06 PM, Clem Cole <clemc at ccc.com> wrote:
>
>
> On Sun, Sep 3, 2017 at 11:08 AM, Warner Losh <imp at bsdimp.com> wrote:
>
>>
>>
>> On Sat, Sep 2, 2017 at 8:54 PM, Dave Horsfall <dave at horsfall.org> wrote:
>>
>>> On Sat, 2 Sep 2017, Nemo wrote:
>>>
>>> Hhhmmm... This begs the historical question: When did LF replace CR/LF
>>>> in UNIX?
>>>>
>>>
>>> Unix has always used NL as the terminator :-)
>>
>>
>> <CR><LF> was the line terminator in DEC operating systems that grew up
>> around the same time as Unix. CP/M and MS-DOS inherited that from them
>> since those systems were developed, in part, using cross compilers running
>> on DEC gear with DEC OSes. Unix came from the Multics world where LF was
>> used as the line terminator... Thankfully, neither CP/M nor MS-DOS picked
>> up DEC's RMS...
>>
>> Warner
>>
> The fun story on that Warner is after years of dogged defense of RMS,
> when C was written for VMS, Cutler had to add Stream I/O. The moment is
> was released, much (?most?) of customer base (including a lot of internal
> folks like the compiler runtime and DB folks) switched to using it. It
> was so much easier. I never heard Dave back down, but it I used to smile
> when I saw the statistics.
>
We got the first release of VAX-C for VMS at school. It didn't have the
Stream I/O mode and all kinds of software was totally broken. There were
stern warnings in the release notes about this as well, IIRC. However, in
the next release it required an upgrade to the next rev of VMS since the C
runtime now depended on the Stream I/O features and all those programs that
were broken mostly worked w/o change. Took another few releases before
things liked exit() worked in a Unix-y way rather than as a thin wrapper
for SYS$EXIT() and such...
Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170903/0d0f5de0/attachment-0001.html>
next prev parent reply other threads:[~2017-09-03 21:42 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 [this message]
2017-09-04 17:29 ` Paul Winalski
2017-09-04 18:34 ` Clem Cole
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='CANCZdfpD7yQp0ZHo6HcZQSch=K-RXTf8sXiELU8MtZ_ZbDb1eg@mail.gmail.com' \
--to=imp@bsdimp.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).