The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem cole <clemc@ccc.com>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] C++ / Kernel
Date: Thu, 23 Aug 2018 23:04:59 -0400	[thread overview]
Message-ID: <0889FBDD-A68B-4062-AF63-EBF4CAB17F8A@ccc.com> (raw)
In-Reply-To: <CAEoi9W7EhwTdJSpYLyoz5rEGUWuRTdEpB9LyZVMuLoY7W=rkdg@mail.gmail.com>

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

Interesting. Void is missing, not just void*? At one point void worked but the void * idiom was buggy/missing    

The problem I have is the compiler was changing in small ways with each version and the differences run together 


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

> On Aug 23, 2018, at 9:58 PM, Dan Cross <crossd@gmail.com> wrote:
> 
>> On Thu, Aug 23, 2018 at 6:17 PM <ron@ronnatalie.com> wrote:
>> [snip]
>> 
>> Void* came out with the V7 compiler, if I recall properly.   The BSD kernel
>> looks as if it requires such a later compiler (it uses bit fields which the
>> earlier compilers didn't support).
>> But it doesn't matter.   You are right char* (or caddr_t) would work just
>> fine for this albeit with some explicit casting.
> 
> This appears to be incorrect, unfortunately. I just tested on the PDP-11/70 running 7th Edition at the Living Computer Museum (I've got an account there) and it appears that neither `cc` nor `pcc` understand `void`.
> 
> Perhaps Steve Johnson can chime in on this? I suspect he'd know the history here well.
> 
>         - Dan C.
> 

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

  reply	other threads:[~2018-08-24  3:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2018-08-24 14:01         ` Dan Cross
2018-08-24 13:22 ` Derek Fawcus
2018-08-24 16:59   ` Steffen Nurpmeso
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-24  1:27 Noel Chiappa
2018-08-24  2:52 ` Clem cole
2018-08-24  7:30 Paul Ruizendaal

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=0889FBDD-A68B-4062-AF63-EBF4CAB17F8A@ccc.com \
    --to=clemc@ccc.com \
    --cc=crossd@gmail.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).