From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Unix source code archive in the news
Date: Sun, 7 Oct 2018 07:23:44 -0400 (EDT) [thread overview]
Message-ID: <20181007112344.0398D18C08F@mercury.lcs.mit.edu> (raw)
> From: jsteve
> I'd say TripOS. There is some surce fragments but I never could get any
> BCPL to cross build anything.
I'm somewhat stunned to hear that, given that Martin Richards did both! What kind
of things are the compilers complaining about? (And I'm also kind of amazed that
Cambridge didn't make an effort to save Tripos.)
Noel
next reply other threads:[~2018-10-07 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 11:23 Noel Chiappa [this message]
2018-10-07 11:48 ` arnold
2018-10-08 10:03 ` Tony Finch
[not found] <mailman.1.1538877601.18358.tuhs@minnie.tuhs.org>
2018-10-07 2:31 ` Paul McJones
-- strict thread matches above, loose matches on Subject: below --
2018-10-07 1:04 Noel Chiappa
2018-10-07 4:08 ` Lars Brinkhoff
2018-10-07 4:56 ` jsteve
2018-10-07 0:00 Nelson H. F. Beebe
2018-10-07 0:07 ` Nigel Williams
2018-10-07 0:55 ` William Corcoran
2018-10-07 1:28 ` Andy Kosela
2018-10-08 5:34 ` Dave Horsfall
2018-10-08 5:55 ` Steve Nickolas
2018-10-09 23:02 ` Dave Horsfall
2018-10-10 0:11 ` Cornelius Keck
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=20181007112344.0398D18C08F@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).