From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Another question about lambdas
Date: Mon, 12 Dec 2022 02:56:03 +0100 [thread overview]
Message-ID: <871qp5o05o.fsf@web.de> (raw)
In-Reply-To: Y5WAlJv0bqddwYH1@tuxteam.de
<tomas@tuxteam.de> writes:
> (now let me get out of the trap: I have to admit that I didn't stop
> to think about dynamic binding).
At university I learned that lexical binding would be more intuitive to
understand, but harder to implement. I thought I was special because I
always found dynamic binding more intuitive. I thought it was because I
learned Lisp mostly by using Emacs, at a time where lexical binding was
only available using a strange thing called `lexical-let' (AFAIR you had
to require cl to use it).
But it seems that dynamic binding is the more intuitive scoping rule for
a lot of people. And a lot have their problems with lexical binding and
closures.
Michael.
next prev parent reply other threads:[~2022-12-12 1:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 17:23 Another question about lambdas Michael Heerdegen
2022-12-10 19:33 ` tomas
2022-12-10 20:29 ` Michael Heerdegen
2022-12-10 20:03 ` Emanuel Berg
2022-12-12 1:50 ` Michael Heerdegen
2023-01-18 11:52 ` Emanuel Berg
2023-01-19 13:23 ` Michael Heerdegen
2022-12-10 21:58 ` Arash Esbati
2022-12-11 0:00 ` Michael Heerdegen
2022-12-11 0:09 ` Michael Heerdegen
2022-12-11 7:02 ` tomas
2022-12-12 1:56 ` Michael Heerdegen [this message]
2022-12-12 5:24 ` tomas
2022-12-12 6:22 ` Michael Heerdegen
2023-01-18 11:51 ` Emanuel Berg
2023-01-19 13:24 ` Michael Heerdegen
2023-01-19 13:38 ` Michael Heerdegen
2023-01-30 17:44 ` Emanuel Berg
2023-02-03 0:20 ` Michael Heerdegen
2023-02-25 7:31 ` Emanuel Berg
2023-02-27 8:28 ` tomas
2023-01-18 11:47 ` Emanuel Berg
2023-01-18 11:33 ` Emanuel Berg
2023-01-19 13:32 ` Michael Heerdegen
2022-12-13 11:26 ` Arash Esbati
2022-12-14 2:22 ` Michael Heerdegen
2022-12-11 0:13 ` Gregory Heytings
2022-12-11 0:38 ` Michael Heerdegen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qp5o05o.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).