From: Clem Cole <clemc@ccc.com>
To: Ron Natalie <ron@ronnatalie.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Typesetter C Compiler and Troff (Re: Re: v6 Unix Documents)
Date: Sun, 1 Dec 2024 12:24:16 -0500 [thread overview]
Message-ID: <CAC20D2MXqcQ43zmzd7jyEELRsUOPAveU+AqCsDDTMFNjXfJQ0g@mail.gmail.com> (raw)
In-Reply-To: <em34270a18-fa36-4c8a-9e4a-ff312a7c2682@2719b2c1.com>
[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]
Exactly -- remember Dennis and Brian wrote K&R in 1978 on V6, not PWB and
not V7 (or anything from Summit like TS). When Brian's typesetter
independent troff was released, that updated language was needed. That
was what we referred to as "typesetter C". Brian and Dennis would have put
together that kit. My >>guess<< is that Mashey et al. and the Summit
folks forked Dennis compiler somewhere before this time -- so what got
packaged with the typesetter kit vs what got packed with Mashey and the
team's kit are close but >>slightly<< different.
ᐧ
On Sun, Dec 1, 2024 at 10:49 AM Ron Natalie <ron@ronnatalie.com> wrote:
> Agreed, the typesetter C ran on a virgin V6 system. That was the whole
> point. It came out before most of us got real V7s.
>
>
>
> ------ Original Message ------
> From "Noel Chiappa" <jnc@mercury.lcs.mit.edu>
> To tuhs@tuhs.org
> Cc jnc@mercury.lcs.mit.edu
> Date 11/30/2024 11:21:31 PM
> Subject [TUHS] Re: Typesetter C Compiler and Troff (Re: Re: v6 Unix
> Documents)
>
> > > From:
> >
> > > I was able to rebuild both the UNSW and the native PWB compiler on
> PWB
> > > 1.0, but not to backport either to vanilla v6.
> >
> >Any idea what the problem was? I'm curious, because we ran a version of
> the
> >Typesetter compiler on the MIT systems, which ran an enhanced V6.
> >
> > Noel
> >
>
[-- Attachment #2: Type: text/html, Size: 2403 bytes --]
next prev parent reply other threads:[~2024-12-01 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-01 4:21 Noel Chiappa
2024-12-01 15:40 ` Ron Natalie
2024-12-01 17:24 ` Clem Cole [this message]
2024-12-01 17:27 ` Clem Cole
2024-12-05 6:38 ` Dan Plassche
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 2:19 [TUHS] v6 Unix Documents Dan Plassche
2024-10-18 13:58 ` [TUHS] " G. Branden Robinson
2024-10-19 3:36 ` Jonathan Gray
[not found] ` <f4e18bf1-98bb-8844-c102-2a1b00fbab15@gmail.com>
2024-10-20 9:39 ` Jonathan Gray
2024-10-21 0:30 ` [TUHS] Typesetter C Compiler and Troff (Re: Re: v6 Unix Documents) Dan Plassche
2024-10-21 2:47 ` [TUHS] " Jonathan Gray
2024-12-01 3:28 ` Dan Plassche
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=CAC20D2MXqcQ43zmzd7jyEELRsUOPAveU+AqCsDDTMFNjXfJQ0g@mail.gmail.com \
--to=clemc@ccc.com \
--cc=ron@ronnatalie.com \
--cc=tuhs@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).