From: Toby Thain <toby@telegraphics.com.au>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, tuhs@tuhs.org
Subject: Re: [TUHS] Happy birthday, John Backus!
Date: Tue, 4 Dec 2018 10:18:48 -0500 [thread overview]
Message-ID: <c00f33c5-cf51-cd36-2426-d6ac72de93ef@telegraphics.com.au> (raw)
In-Reply-To: <20181204144306.A830E18C0A0@mercury.lcs.mit.edu>
On 2018-12-04 9:43 AM, Noel Chiappa wrote:
> > From: Toby Thain
>
> > He made amends by being early to recognise that problem, and propose
> > solutions, in his 1977 ACM Turing Award lecture
>
> Actually, I'd consider a far bigger amend to be his work on Algol 60 (he was
Possibly, but it's far harder to unpack thesis and reasoning from a
codebase.
> one of the main contributors), which Hoare so memorably described as "a
> language so far ahead of its time that it was not only an improvement on its
> predecessors but also on nearly all its successors".
> ...
>
> Noel
>
next prev parent reply other threads:[~2018-12-04 15:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 14:43 Noel Chiappa
2018-12-04 14:53 ` Clem Cole
2018-12-04 16:24 ` Tim Rylance
2018-12-04 16:53 ` Clem Cole
2018-12-04 17:46 ` Paul Winalski
2018-12-04 20:59 ` Paul Winalski
2018-12-04 22:49 ` [TUHS] Tandem NSK implementation language (was: Happy birthday, John Backus!) Greg 'groggy' Lehey
2018-12-05 0:08 ` Paul Winalski
2018-12-05 17:49 ` [TUHS] Happy birthday, John Backus! Paul Winalski
2018-12-04 15:18 ` Toby Thain [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-02 22:17 Dave Horsfall
2018-12-02 22:34 ` Toby Thain
2018-12-03 1:32 ` Rob Pike
2018-12-03 4:11 ` Toby Thain
2018-12-03 4:27 ` Rob Pike
2018-12-03 13:10 ` John P. Linderman
2018-12-03 22:44 ` ron
2018-12-03 16:25 ` Clem Cole
2018-12-03 20:20 ` Paul Winalski
2018-12-03 20:37 ` Clem Cole
2018-12-03 20:46 ` Hellwig Geisse
2018-12-03 22:24 ` Paul Winalski
2018-12-03 23:00 ` Lawrence Stewart
2018-12-04 11:53 ` Tony Finch
2018-12-04 14:23 ` Clem Cole
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=c00f33c5-cf51-cd36-2426-d6ac72de93ef@telegraphics.com.au \
--to=toby@telegraphics.com.au \
--cc=jnc@mercury.lcs.mit.edu \
--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).