The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] Happy birthday, Niklaus Wirth!
Date: Fri, 16 Feb 2018 05:34:56 -0800	[thread overview]
Message-ID: <20180216133512.24B19156E811@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 16 Feb 2018 12:37:39 +0000." <3A4DF9EC-F287-4CD9-85E8-21EE729B37ED@tfeb.org>

On Fri, 16 Feb 2018 12:37:39 +0000 tfb at tfeb.org wrote:
tfb at tfeb.org writes:
> 
> On 16 Feb 2018, at 12:10, Bakul Shah <bakul at bitblocks.com> wrote:
> >=20
> > Now you may quibble about "came from"=20
> 
> I do so quibble.  In particular I quibble that features *that were not
> present in Algol*, such as full continuations (which I think exist in
> the AIM-349 language via CATCH) can have 'come from Algol'.  Full
> continuations are the place where Scheme actually takes lexical scope
> seriously.

They did lexical scoping "right", no doubt. But back when
Landin first found that lambda calculus was useful for
modeling programming languages these concepts were not clearly
understood.  I do not recall reading anything about whether
Algol designers not allowing full lexical scopin was due to an
oversight or realizing that efficient implementation of
functional argument was not possible. May be Algol's call by
name was deemed sufficient? At any rate Algol's not having
full lexical scoping does not mean one can simply reject the
idea of being influenced by it. Often at the start there is
lots of fumbling before people get it right. May be someone
should ask Steele?

And no, I do not think first class continuations automatically
follow from lexical scoping.  Go has lexical scoping including
closures but no call/cc.  The idea of representing future
program state as a function I think comes from Strachey,
Wadsworth and Reynolds. They used it extensively in
denotational semantics to model program behavior.

> But I'm not interested in getting into a fight about this.

We are just presenting our interpretation of history!  Not
that anybody cares!


  reply	other threads:[~2018-02-16 13:34 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
2018-02-16 12:10           ` Bakul Shah
2018-02-16 12:37             ` tfb
2018-02-16 13:34               ` Bakul Shah [this message]
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=20180216133512.24B19156E811@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    /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).