The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: arnold@skeeve.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Looking for final C compiler by Dennis Ritchie
Date: Thu, 19 Jul 2018 20:23:53 +0100	[thread overview]
Message-ID: <CACXZuxdWEuznnahktRSfNgdYMQdh_d46HDBJuDr7mOVpTKxUYQ@mail.gmail.com> (raw)
In-Reply-To: <201807190541.w6J5foDw018028@freefriends.org>

On 19 July 2018 at 06:41,  <arnold@skeeve.com> wrote:
> Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
>> I am interested in finding out if the last C compiler code (not the
>> earliest versions which I know
>> are available) written by Dennis Ritchie is available somewhere. I
>> assume that the C compiler in V7 code was written by him?
>>
> Yes - but take note, that would be 'cc'.  The 'pcc' command, also in
> V7, is Steve Johnson's Portable C Compiler.
>

Many thanks.

I was also wondering if the C pre-processor included in lcc project
was written by Dennis:
https://github.com/drh/lcc/tree/master/cpp

I seem to have read somewhere that it was - but I cannot locate any
reference to that.

Thanks and Regards
Dibyendu

  reply	other threads:[~2018-07-19 19:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 21:37 Dibyendu Majumdar
2018-07-19  5:41 ` arnold
2018-07-19 19:23   ` Dibyendu Majumdar [this message]
2018-07-20 22:04     ` Dibyendu Majumdar
2018-07-19 14:50 ` Clem Cole
2018-07-19 19:40   ` Dibyendu Majumdar
2018-07-20 10:04 Paul Ruizendaal
2018-07-20 19:57 ` Dibyendu Majumdar
2018-07-22 20:49 ` Dibyendu Majumdar
2018-07-23  9:24   ` Paul Ruizendaal
2018-07-23 10:28     ` arnold
2018-07-23 19:35       ` Dibyendu Majumdar
2018-07-24  6:37         ` arnold
2018-07-23 15:12   ` Clem Cole
2018-07-23 15:55     ` Larry McVoy
2018-07-23 19:29     ` Dibyendu Majumdar
2018-07-23 20:12     ` Bakul Shah
2018-07-23 20:48       ` Dibyendu Majumdar

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=CACXZuxdWEuznnahktRSfNgdYMQdh_d46HDBJuDr7mOVpTKxUYQ@mail.gmail.com \
    --to=mobile@majumdar.org.uk \
    --cc=arnold@skeeve.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).