The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: TUHS <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] C++ / Kernel
Date: Thu, 23 Aug 2018 19:05:19 -0700	[thread overview]
Message-ID: <7A7BA7E4-8854-4744-B3B0-9C83D061FB64@bitblocks.com> (raw)
In-Reply-To: <CAC20D2PR5eQ7bjod9dKWf7tk55TaqQb3p8rR7saQxCEEMM3UeA@mail.gmail.com>

In Henry Spencer's v7 sources there is a "struct void" in
cmd/sh/mode.h -- may have to do Bourne's fascination with
Algol68!

Bitfields were available but they were not used in v7 sources.
May be because v7 pcc generated slow code for bitfields access.
[Gosling's emacs used bitfields extensively. I managed to
compile it but it ran extremely slowly on a 5.6Mhz Fortune
box. That was the main reason I didn't switch to emacs. Then
Yost brought along the Rand editor and I used it until it
would no longer compile on *BSDs.]

> On Aug 23, 2018, at 5:30 PM, Clem Cole <clemc@ccc.com> wrote:
> 
> 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.   
> 
> On Thu, Aug 23, 2018 at 7:42 PM <ron@ronnatalie.com> wrote:
> 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
> 
> -- 
> Sent from a handheld expect more typos than usual


  reply	other threads:[~2018-08-24  2:05 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
2018-08-24  0:30   ` Clem Cole
2018-08-24  2:05     ` Bakul Shah [this message]
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=7A7BA7E4-8854-4744-B3B0-9C83D061FB64@bitblocks.com \
    --to=bakul@bitblocks.com \
    --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).