From: paul@mcjones.org (Paul McJones)
Subject: [TUHS] I just noticed all the cfont aka C++ in research
Date: Wed, 5 Apr 2017 19:42:13 -0700 [thread overview]
Message-ID: <B3B2E3D6-EBEF-49D7-902A-F0A7A33A6374@mcjones.org> (raw)
In-Reply-To: <mailman.721.1491445316.3779.tuhs@minnie.tuhs.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
> I suppose that it would make sense that all of AT&T's leading edge projects would use research Unix. I've always heard of the original C++ to C translator but this is the first time I've actually seen it.
In case you’re interested, Bjarne Stroustrup has been helping me collect early versions of cfront here:
http://www.softwarepreservation.org/projects/c_plus_plus/#cfront
Previously we had located a listing of Release E (which we scanned), source for Release 1.0 of 10/10/85, and source for Release 3.0.3. From these 9th and 10th edition snapshots, cfront 1.2.2 6/10/87, AT&T C++ Translator 2.00 06/30/89, AT&T C++ Translator 2.1.0+ 04/01/90, and AT&T C++ Translator 2.1++ 08/24/90 join the list.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170405/50486227/attachment.html>
next parent reply other threads:[~2017-04-06 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.721.1491445316.3779.tuhs@minnie.tuhs.org>
2017-04-06 2:42 ` Paul McJones [this message]
2017-04-06 3:20 Jason Stevens
-- strict thread matches above, loose matches on Subject: below --
2017-04-06 2:15 Jason Stevens
2017-04-06 2:20 ` Noel Hunt
2017-04-06 2:21 ` Jason Stevens
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=B3B2E3D6-EBEF-49D7-902A-F0A7A33A6374@mcjones.org \
--to=paul@mcjones.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).