From: Angelo Papenhoff <aap@papnet.eu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] VCF East
Date: Tue, 7 May 2019 18:36:12 +0200 [thread overview]
Message-ID: <20190507163612.GA29343@indra.papnet.eu> (raw)
In-Reply-To: <20190507163224.A02DD18C091@mercury.lcs.mit.edu>
On 07/05/19, Noel Chiappa wrote:
> The 'grep' story was amusing, but historically, probably the most valuable
> thing was the detail on the origins of B - DMR's paper on early C ("The
> Development of the C Language") mentions the FORTRAN, but doesn't give the
> detail on why that got canned, and B appeared instead.
I was also quite surprised by that. No mention of BCPL...
Great video, really loved it.
next prev parent reply other threads:[~2019-05-07 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 16:32 Noel Chiappa
2019-05-07 16:36 ` Angelo Papenhoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-14 13:41 Doug McIlroy
2019-05-14 19:36 ` Ralph Corderoy
2019-05-14 21:01 ` Jon Steinhart
2019-05-14 21:48 ` Rob Pike
2019-05-07 12:50 John P. Linderman
2019-05-07 14:17 ` Dan Cross
2019-05-07 14:33 ` David
2019-05-12 8:07 ` Arno Griffioen
2019-05-12 12:09 ` Rob Pike
2019-05-12 12:36 ` Ralph Corderoy
2019-05-13 12:48 ` Rob Pike
2019-05-13 16:26 ` Jon Steinhart
2019-05-07 16:51 ` arnold
2019-05-07 17:04 ` Anthony Martin
2019-05-10 4:45 ` Greg 'groggy' Lehey
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=20190507163612.GA29343@indra.papnet.eu \
--to=aap@papnet.eu \
--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).