The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Jaap Akkerhuis <jaapna@xs4all.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Question: stdio - Who invented and ...
Date: Mon, 23 Mar 2020 10:45:48 -0400	[thread overview]
Message-ID: <CAC20D2N1PAquFJFcu=_2yN3TEqzM703SX_Zu8YdBmm0T4F2A+Q@mail.gmail.com> (raw)
In-Reply-To: <01040037-4D96-4DCB-8E40-B418E424C0F5@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]

On Mon, Mar 23, 2020 at 10:24 AM Jaap Akkerhuis <jaapna@xs4all.nl> wrote:

> Yes, "Typesetter C" was to accommodate the C Version of troff written
> by Ossana and I checked the source, it doesn't use stdio.
>
Interesting.   The compiler described in K&R was a v6 compiler -- we had it
at CMU before we had V7.  I thought we got it from the Typesetter C
release.  But Ted may have brought even before that.   Brian K. might have
also.  He was Brian Ried's thesis committee and was coming to CMU
reasonably often in 77/78 timeframe - when Reid was writing Scribe and
Brian ditroff.  I'm pretty sure we got some stuff via that channel too, as
I was the person moving some of that around campus and its how I first met
Brian.

I admit that I might have some void in my memory, but I do remember part of
this pretty well.  Because CS had the 11/40E with writable microcode (they
had been developed for C.mmp). The CS PDP-11's running UNIX (IUS and SUS)
had CSV/CRET instructions (as well as a couple of others for BLISS and
support capabilities, IIRC). Someone (Paul Rubin I think), had modified the
original V6 compiler to generate CSV/CRET.  That meant that binaries from
CS would not run on the 11/34's which most of the UNIX box on campus had by
then become.  Ted and I were in EE and there was a small battle as to which
systems were more current.  Since Ted worked officially for USG, he had a
direct line to much of there stuff.    Ted had xerographic proofs of the
book when it was being reviewed BTW.   When CMU got the new Ritchie
compiler and I had the task of rippling it out to all the sites in EE,
Mellon Institute, et al.  CS did not pick it up originally because it did
not have the CSAV/CRET changes.   CMU did not get V7 until late winter
'78/early spring '79 around the time I was leaving.

So, we definitely had a Ritchie based K&R compiler with stdio.  I had
thought that come to us with Typesetter C, but it sounds like it had a
different path.   FWIW: that would actually be the compiler sources I
started with at Tektronix 6 months later, when I started to retarget it for
what would become the 68000 (it was not yet released and was an
experimental chip), as I had brought the CMU UNIX systems with me.

[-- Attachment #2: Type: text/html, Size: 3205 bytes --]

  reply	other threads:[~2020-03-23 14:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 10:18 Ed Bradford
2020-03-23 10:32 ` arnold
2020-03-23 13:46   ` Clem Cole
2020-03-23 13:59     ` arnold
2020-03-23 14:24       ` Jaap Akkerhuis
2020-03-23 14:45         ` Clem Cole [this message]
2020-03-23 18:47         ` Richard Salz
2020-03-23 19:22           ` Jaap Akkerhuis
2020-03-23 21:38     ` Dave Horsfall
2020-03-24  2:02     ` Greg A. Woods
2020-05-11  1:00       ` scj

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='CAC20D2N1PAquFJFcu=_2yN3TEqzM703SX_Zu8YdBmm0T4F2A+Q@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=jaapna@xs4all.nl \
    --cc=tuhs@minnie.tuhs.org \
    /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).