From: <ron@ronnatalie.com>
To: "'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>, <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] C++ / Kernel
Date: Thu, 23 Aug 2018 19:42:19 -0400 [thread overview]
Message-ID: <160c01d43b3a$ef02ff40$cd08fdc0$@ronnatalie.com> (raw)
In-Reply-To: <20180823232936.8F04818C088@mercury.lcs.mit.edu>
Void probably showed up their first as well It was more like modern C
than the V6 compiler.
-----Original Message-----
From: TUHS <tuhs-bounces@minnie.tuhs.org> On Behalf Of Noel Chiappa
Sent: Thursday, August 23, 2018 7:30 PM
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] C++ / Kernel
> From: Ron Natalie
> The BSD kernel looks as if it requires such a later compiler (it uses
> bit fields which the earlier compilers didn't support).
Umm, minor nit: bit fields were added to/as of 'Typesetter C', which I
gather was intermediate between V6 and V7.
Noel
next prev parent reply other threads:[~2018-08-23 23:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 23:29 Noel Chiappa
2018-08-23 23:42 ` ron [this message]
2018-08-24 0:30 ` Clem Cole
2018-08-24 2:05 ` Bakul Shah
2018-08-24 12:21 ` ron
-- strict thread matches above, loose matches on Subject: below --
2018-08-24 7:30 Paul Ruizendaal
2018-08-24 1:27 Noel Chiappa
2018-08-24 2:52 ` Clem cole
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='160c01d43b3a$ef02ff40$cd08fdc0$@ronnatalie.com' \
--to=ron@ronnatalie.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).