From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] Happy birthday, Niklaus Wirth!
Date: Fri, 16 Feb 2018 10:01:36 +0000 [thread overview]
Message-ID: <98310912-009A-438C-B7C6-82C8DF25621B@tfeb.org> (raw)
In-Reply-To: <20180216020944.AF0ED156E80B@mail.bitblocks.com>
On 16 Feb 2018, at 02:09, Bakul Shah <bakul at bitblocks.com> wrote:
>
> Scheme's lexical scope and block structure came from Algol.
> The rest from Lisp. The joke was that the shortest and longest
> language specs were of lisp dialects. The C++ spec may be
> longer now.
I don't think this is true in any meaningful sense. There are famous plays on words which relate Scheme to Algol (The Scheme specifications are 'revised^n reports on the algorithmic language scheme', and I think lexical scope in Lisps probably originated with the Scheme people, but Scheme was the first standard language, anywhere, which took lexical scope seriously: in particular it was the first standard language with first-class continuations. (I'm saying 'standard language' because I'm sure there were research prototype implementations.).
The Common Lisp spec was very long at the time -- I think it was 1100 pages. It was mostly as long as it was because they decided not to split out what other languages would call parts of the standard library.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180216/5f246f0a/attachment.html>
next prev parent reply other threads:[~2018-02-16 10:01 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 21:06 Dave Horsfall
2018-02-14 21:12 ` Clem Cole
2018-02-14 22:15 ` George Michaelson
2018-02-14 23:37 ` Dave Horsfall
2018-02-14 21:24 ` Toby Thain
2018-02-16 0:01 ` Dave Horsfall
2018-02-16 0:51 ` Dan Cross
2018-02-16 1:06 ` Clem cole
2018-02-16 3:10 ` Toby Thain
2018-02-16 13:36 ` Clem Cole
2018-02-16 1:18 ` Larry McVoy
2018-02-16 1:55 ` George Michaelson
2018-02-16 1:56 ` Lawrence Stewart
2018-02-16 2:38 ` Dan Cross
2018-02-16 2:41 ` Larry McVoy
2018-02-16 2:51 ` Dan Cross
2018-02-16 2:56 ` George Michaelson
2018-02-16 2:51 ` [TUHS] Clueless programmers - was " Toby Thain
2018-02-16 2:55 ` Larry McVoy
2018-02-16 10:26 ` [TUHS] " Tim Bradshaw
2018-02-16 1:25 ` Ian Zimmerman
2018-04-24 0:59 ` Ian Zimmerman
2018-04-24 3:26 ` Dave Horsfall
2018-04-24 4:31 ` Dan Stromberg
2018-04-24 13:42 ` Clem Cole
2018-02-16 2:09 ` Bakul Shah
2018-02-16 2:31 ` Toby Thain
2018-02-16 10:01 ` Tim Bradshaw [this message]
2018-02-16 12:10 ` Bakul Shah
2018-02-16 12:37 ` tfb
2018-02-16 13:34 ` Bakul Shah
2018-02-16 14:07 ` Bakul Shah
2018-02-16 20:13 ` tfb
2018-02-16 3:17 ` Dan Stromberg
2018-02-14 23:19 ` Greg 'groggy' Lehey
2018-02-14 23:31 ` Dave Horsfall
2018-02-15 17:32 ` Steffen Nurpmeso
2018-02-15 19:18 ` Ian Zimmerman
2018-02-15 20:56 ` Steffen Nurpmeso
2018-02-15 21:31 ` Jeremy C. Reed
2018-02-15 2:30 ` Nemo
2018-02-16 2:19 Noel Chiappa
2018-02-16 2:48 ` Larry McVoy
2018-02-16 4:19 ` Steve Nickolas
2018-02-16 11:27 ` Tim Bradshaw
2018-02-16 15:45 ` Nemo
[not found] <mailman.1.1518746401.1018.tuhs@minnie.tuhs.org>
2018-02-16 2:40 ` Paul McJones
2018-02-16 13:42 Noel Chiappa
2018-02-16 21:02 ` Tim Bradshaw
[not found] <mailman.22.1518790085.20342.tuhs@minnie.tuhs.org>
2018-02-16 17:40 ` Paul McJones
2018-02-16 19:24 ` Bakul Shah
2018-02-18 20:50 Norman Wilson
2018-02-19 0:28 ` Dave Horsfall
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=98310912-009A-438C-B7C6-82C8DF25621B@tfeb.org \
--to=tfb@tfeb.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).