From: John Foust via TUHS <tuhs@tuhs.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: History of non-Bell C compilers?
Date: Fri, 08 Mar 2024 08:03:23 -0600 [thread overview]
Message-ID: <170990678456.1947684.3255210399998147395@minnie.tuhs.org> (raw)
In-Reply-To: <a356ce42-779b-ae35-19fe-7e7844b83c86@makerlisp.com>
At 05:56 PM 3/7/2024, Luther Johnson wrote:
>Speaking of the CP/M and later DOS world, Aztec C was a very competent C
>compiler. I recently put together a CP/M environment, and used the
>latest version I could find of Aztec C, and it did just what I wanted it
>to do.
There is an extensive web with the history of Aztec C.
https://www.aztecmuseum.ca/
I don't see any Unix products there, but I have a vague memory of
one of the compiler developers telling me about how they bootstrapped
on a PDP.
- John
next prev parent reply other threads:[~2024-03-08 14:06 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 23:14 [TUHS] " Tom Lyon
2024-03-07 23:24 ` [TUHS] " Warner Losh
2024-03-07 23:39 ` Dave Horsfall
2024-03-07 23:49 ` Larry McVoy
2024-03-07 23:56 ` Luther Johnson
2024-03-08 14:03 ` John Foust via TUHS [this message]
2024-03-07 23:59 ` Greg 'groggy' Lehey
2024-03-08 0:08 ` Rich Salz
2024-03-08 0:30 ` Warner Losh
2024-03-08 0:57 ` Rob Pike
2024-03-08 1:08 ` Bakul Shah via TUHS
2024-03-08 1:10 ` Rob Pike
2024-03-08 1:12 ` Rob Pike
2024-03-08 1:22 ` Bakul Shah via TUHS
2024-03-08 9:33 ` arnold
2024-03-08 9:45 ` Wesley Parish
2024-03-08 13:06 ` Luther Johnson
2024-03-08 18:33 ` William H. Mitchell
2024-03-10 3:14 ` Adam Thornton
2024-03-11 22:21 ` Phil Budne
2024-03-07 23:52 ` Warner Losh
2024-03-08 0:15 ` Charles H Sauer (he/him)
2024-03-08 0:30 ` Marc Rochkind
2024-03-08 0:54 ` Heinz Lycklama
2024-03-08 1:48 ` segaloco via TUHS
2024-03-08 2:12 ` Tom Lyon
2024-03-08 2:13 ` Lawrence Stewart
2024-03-08 3:15 ` Jonathan Gray
2024-03-07 23:24 ` Luther Johnson
2024-03-07 23:27 ` Luther Johnson
2024-03-07 23:44 ` Tom Lyon
2024-03-08 0:24 ` Marc Rochkind
2024-03-08 1:27 ` Jeffry R. Abramson
2024-03-10 2:13 ` Greg A. Woods
2024-03-08 2:26 ` Will Senn
2024-03-08 3:03 ` Peter Yardley
2024-03-08 3:28 ` George Michaelson
2024-03-08 3:58 ` Luther Johnson
2024-03-08 5:53 ` Lars Brinkhoff
2024-03-08 13:42 ` Henry Bent
2024-03-08 14:00 ` arnold
2024-03-08 14:16 ` Warner Losh
2024-03-08 15:44 ` Paul Winalski
2024-03-08 17:18 ` Adam Thornton
2024-03-10 2:31 ` Damian Wildie
2024-03-11 17:12 Paul Ruizendaal
2024-03-11 20:44 ` Marc Rochkind
2024-03-11 22:28 ` Peter Yardley
2024-03-12 0:30 ` ron minnich
2024-03-12 13:31 ` Larry Stewart
2024-03-12 16:41 ` Paul Winalski
2024-03-12 14:55 ` Henry Bent
2024-03-12 17:17 ` Marc Rochkind
2024-03-13 14:37 ` Clem Cole
2024-03-13 15:28 ` Marc Rochkind
2024-03-13 15:33 ` Warner Losh
2024-03-13 15:53 ` Clem Cole
2024-03-12 15:42 ` Paul Ruizendaal
2024-03-12 23:08 Steve Simon
[not found] <aee297f1-2f6a-4620-87f7-f1672ae03b61@osta.com>
2024-03-15 3:34 ` Heinz Lycklama
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=170990678456.1947684.3255210399998147395@minnie.tuhs.org \
--to=tuhs@tuhs.org \
--cc=jfoust@threedee.com \
/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).