The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] C++ / Kernel
Date: Thu, 23 Aug 2018 22:52:24 -0400	[thread overview]
Message-ID: <DC7AB6CC-BC48-43DA-8595-2B98A1EA49EC@ccc.com> (raw)
In-Reply-To: <20180824012730.5945A18C088@mercury.lcs.mit.edu>

As I said I’m not sure but I thought I remember them being there.  I no longer have that distribution tape so I cannot diff it.  

If i recall the order the three Ritchie compilers we had that supported stdio were typesetter, Unix/TS and then finally 7th Edition.  I remember they we all slightly different but don’t remember what they the differences were.  

As Steve has previously said Dennis was constantly improving the compiler, so I suspect it was just the state of the world when those snapshots were taken.  

The big changes to the language were between 6th Edition and Typesetter which were done in concert if not to support Brian’s work on the troff rewrite.  Plus the first draft of book was being written around then also. 

The book definitely predates 7th edition’s release which I date because we did not get Seventh Edition until spring 79 and Ted had xeroxgraphic copies of the book at least a year earlier, which was when we were running TS which he had brought from the Labs.  

Clem

Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 

On Aug 23, 2018, at 9:27 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:

>> From: Clem Cole
> 
>> Im pretty sure I remember void being in typesetter C also.
> 
> Hmm. In the two original 'help' files I have about the changes to C (the term
> 'typesetter C' doesn't appear, but it's pretty clear that's what the subject
> is), available through here:
> 
>  http://gunkies.org/wiki/Typesetter_C
> 
> the term 'void' does not appear (although most other stuff - e.g. unions, bit
> fields, typedef, yadda yadda - does).
> 
>    Noel

  reply	other threads:[~2018-08-24  2:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  1:27 Noel Chiappa
2018-08-24  2:52 ` Clem cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-24  7:30 Paul Ruizendaal
2018-08-23 23:29 Noel Chiappa
2018-08-23 23:42 ` ron
2018-08-24  0:30   ` Clem Cole
2018-08-24  2:05     ` Bakul Shah
2018-08-24 12:21     ` ron
2018-08-23 14:42 ron
2018-08-23 17:24 ` Clem Cole
2018-08-23 20:21 ` Bakul Shah
2018-08-23 22:17   ` ron
2018-08-23 22:28     ` Nevin Liber
2018-08-23 22:48       ` Clem Cole
2018-08-23 23:14     ` Steffen Nurpmeso
2018-08-24 14:13       ` Steffen Nurpmeso
2018-08-24 14:32         ` ron
2018-08-24 18:15           ` Steffen Nurpmeso
2018-08-26 16:34             ` Paul Winalski
2018-08-27 16:31               ` Steffen Nurpmeso
2018-08-24  1:41     ` Bakul Shah
2018-08-24 10:41       ` Pete Turnbull
2018-08-24 12:17       ` ron
2018-08-24 18:36         ` Bakul Shah
2018-08-24 18:38           ` ron
2018-08-24  1:58     ` Dan Cross
2018-08-24  3:04       ` Clem cole
2018-08-24 14:01         ` Dan Cross
2018-08-24 13:22 ` Derek Fawcus
2018-08-24 16:59   ` Steffen Nurpmeso

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=DC7AB6CC-BC48-43DA-8595-2B98A1EA49EC@ccc.com \
    --to=clemc@ccc.com \
    --cc=jnc@mercury.lcs.mit.edu \
    --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).