From: wkt@tuhs.org (Warren Toomey)
Subject: [TUHS] C compiler
Date: Tue, 27 Sep 2005 17:44:34 +1000 [thread overview]
Message-ID: <20050927074434.GA10695@minnie.tuhs.org> (raw)
In-Reply-To: <200509271945.04036.wes.parish@paradise.net.nz>
On Tue, Sep 27, 2005 at 07:45:03PM +1200, Wesley Parish wrote:
> B! I would like to have a look at that - that, and NB.
> Does anyone know if they're still extant, or their documentation at the very
> least? (I've seen BCPL, and read some of its documentation, but it's still a
> hop-skip-and-a-jump away from C. Some BCPL things do seem a little bit
> strange to a C user ... ;)
One or both of the referenced articles suggest that all traces have disappeared.
There may be a B or NB language manual laying around... Yes:
http://cm.bell-labs.com/cm/cs/who/dmr/kbman.html and
http://cm.bell-labs.com/cm/cs/who/dmr/bintro.html
Warren
prev parent reply other threads:[~2005-09-27 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 19:28 Bill Cunningham
2005-09-26 22:04 ` Warren Toomey
2005-09-27 7:45 ` Wesley Parish
2005-09-27 7:44 ` Warren Toomey [this message]
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=20050927074434.GA10695@minnie.tuhs.org \
--to=wkt@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).