From: John Cowan <cowan@ccil.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: COFF <coff@minnie.tuhs.org>
Subject: [TUHS] Re: [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary)
Date: Wed, 15 Mar 2023 00:33:17 -0400 [thread overview]
Message-ID: <CAD2gp_Q3VbLitTLy3oFhH22RbGwX8kpqrkWhF=0LK7qfmYACuA@mail.gmail.com> (raw)
In-Reply-To: <20230315035930.C68E018C080@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
[migrating to coff]
On Tue, Mar 14, 2023 at 11:59 PM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
> I do not grant your basic assertion. Hoare had it right: "ALGOL 60 [was] 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." That would definitely
> include Algol68, which was a classic committee-designed nightmare.
>
Common Lisp came long after 1968, was committee-designed, and is by no
means a nightmare. It's not a jewel like Scheme is said to be (wrongly
IMO), it's a ball of mud, but balls of mud are best for solving muddy
problems.
[-- Attachment #2: Type: text/html, Size: 1194 bytes --]
next prev parent reply other threads:[~2023-03-15 4:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 3:59 Noel Chiappa
2023-03-15 4:33 ` John Cowan [this message]
2023-03-16 22:50 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 11:37 [TUHS] Re: I can't drive 55: "GOTO considered harmful" 55th anniversary Noel Chiappa
2023-03-10 15:54 ` Dan Cross
2023-03-12 7:39 ` Anthony Martin
2023-03-12 11:40 ` Dan Cross
2023-03-13 3:25 ` John Cowan
2023-03-13 10:40 ` Alejandro Colomar (man-pages)
2023-03-13 12:19 ` Dan Cross
2023-03-13 12:43 ` [TUHS] [TUHS]: C dialects (was: I can't drive 55: "GOTO considered harmful" 55th anniversary) Alejandro Colomar
2023-03-13 12:46 ` [TUHS] " Dan Cross
2023-03-13 16:00 ` Paul Winalski
2023-03-13 19:00 ` Clem Cole
2023-03-13 19:09 ` Larry McVoy
2023-03-13 19:17 ` Steve Nickolas
2023-03-13 20:26 ` Dan Cross
2023-03-13 22:25 ` Alejandro Colomar (man-pages)
2023-03-13 20:48 ` Paul Winalski
2023-03-13 20:56 ` Bakul Shah
2023-03-14 1:06 ` Larry McVoy
2023-03-13 21:00 ` Paul Winalski
2023-03-13 21:07 ` Bakul Shah
2023-03-13 21:14 ` Dan Cross
2023-03-13 22:15 ` Dave Horsfall
2023-03-13 22:47 ` Dave Horsfall
2023-03-14 0:23 ` Dan Cross
2023-03-14 0:21 ` Dan Cross
2023-03-14 13:52 ` Chet Ramey
2023-03-14 1:27 ` Bakul Shah
2023-03-13 21:28 ` Paul Winalski
2023-03-14 0:38 ` John Cowan
2023-03-14 2:49 ` Theodore Ts'o
2023-03-14 3:06 ` G. Branden Robinson
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='CAD2gp_Q3VbLitTLy3oFhH22RbGwX8kpqrkWhF=0LK7qfmYACuA@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=coff@minnie.tuhs.org \
--cc=jnc@mercury.lcs.mit.edu \
/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).