From: arnold@skeeve.com
To: tuhs@tuhs.org
Subject: [TUHS] changes in C compilers
Date: Fri, 24 Aug 2018 01:02:51 -0600 [thread overview]
Message-ID: <201808240702.w7O72pJT005068@freefriends.org> (raw)
My two cents, ...
> From: Clem Cole <clemc@ccc.com>
> Date: Thu, 23 Aug 2018 20:30:19 -0400
> To: ron@ronnatalie.com
> Subject: Re: [TUHS] C++ / Kernel
>
> Yep. Im pretty sure I remember void being in typesetter C also. IIRC the
> differences between that version of Dennis???s compiler and what was included
> in 7th Edition was mostly in the libraries ie stdio was first released as
> part of the typesetter compiler but it was still a work in progress.
K&R 1 did not have void or structure assignment. Those came later,
although I'm not sure when. They may have been mentioned in an
appendix; my copy isn't handy to check.
At what point did each struct become its own namespace? I think
around the time of K&R1.
> From: Clem cole <clemc@ccc.com>
> Date: Thu, 23 Aug 2018 22:52:24 -0400
> To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
> Subject: Re: [TUHS] C++ / Kernel
>
> ...
>
> 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 troff rewrite was later, circa '81 or so. Definitely NOT in the
V6/V7 timeframe.
Arnold
next reply other threads:[~2018-08-24 7:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 7:02 arnold [this message]
2018-08-24 12:00 ` Clem cole
2018-08-24 13:50 ` [TUHS] changes in C compilers (Typesetter C) Jaap Akkerhuis
2018-08-25 18:30 ` [TUHS] changes in C compilers arnold
2018-08-25 19:58 ` Clem Cole
2018-08-25 22:19 ` John P. Linderman
2018-08-25 23:02 ` Clem Cole
2018-08-25 23:14 Noel Chiappa
2018-08-25 23:56 ` Clem Cole
2018-08-30 20:26 Norman Wilson
2018-08-30 20:48 ` Clem Cole
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=201808240702.w7O72pJT005068@freefriends.org \
--to=arnold@skeeve.com \
--cc=tuhs@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).