From: Clem Cole <clemc@ccc.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] Looking for final C compiler by Dennis Ritchie
Date: Mon, 23 Jul 2018 11:12:49 -0400 [thread overview]
Message-ID: <CAC20D2OTsR0ZxqeUk2EBpZnWy2k4LVf8=VPKzitWhkT3n_vL8g@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxeJ3igMtfbLs1iUPMLhomQUG0dEjpaHHmV0L7hF0bvo4g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 881 bytes --]
On Sun, Jul 22, 2018 at 4:49 PM, Dibyendu Majumdar <mobile@majumdar.org.uk>
wrote:
>
>
> It seems that Dennis Ritchie wrote a paper 'A Tour through the Unix C
> Compiler' which is quite useful in understanding the compiler. I have
> converted the doc to Markdown format as well which makes it easier to
> read.
https://s3-us-west-2.amazonaws.com/belllabs-microsite-plan9/7thEdMan/bswv7.html
You might try downloading the PDF or PS versions of the V7 documents from
amazon. It seems like a lot less work work and will be a lot easier to
read. Also Gnu groff runs on pretty much everything these days, so going
from the V7 troff sources yourself is not difficult; in fact its pretty
smart. Its still the best 'pure document compiler' out there. And it
means you can add your additions/ corrections / notes to what Dennis did
right inline.
ᐧ
[-- Attachment #2: Type: text/html, Size: 1917 bytes --]
next prev parent reply other threads:[~2018-07-23 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2018-07-18 21:37 Dibyendu Majumdar
2018-07-19 5:41 ` arnold
2018-07-19 19:23 ` Dibyendu Majumdar
2018-07-20 22:04 ` Dibyendu Majumdar
2018-07-19 14:50 ` Clem Cole
2018-07-19 19:40 ` 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='CAC20D2OTsR0ZxqeUk2EBpZnWy2k4LVf8=VPKzitWhkT3n_vL8g@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=mobile@majumdar.org.uk \
--cc=pnr@planet.nl \
--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).