From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Another question about lambdas
Date: Thu, 19 Jan 2023 14:32:24 +0100 [thread overview]
Message-ID: <87zgae8xav.fsf@web.de> (raw)
In-Reply-To: 87a62gyt4o.fsf@dataswamp.org
Emanuel Berg <incal@dataswamp.org> writes:
> I mean, why do we have all this f(x) and g() { x } notation in
> programming if it is, or can be, actually the same x as some
> x outside of that? Just looking at it, and writing it, tells
> me, "hey, this is an x of it's own". But with dynamic scope it
> sometimes isn't and you have to look somewhere else, execute
> code in your head etc to find out.
> [...]
>
> > And a lot have their problems with lexical binding
> > and closures.
>
> What do you mean, what's up with them?
As long as there are only individual closures that only treat one
individual variable it's all trivial, yes.
The non-trivial aspects start when several closures, used in different
parts of a program, share the same variables of the same environment,
or partly share an environment partly. Or a variable of the same name
appears multiple times in different environments with different bindings.
The "execute code in your head" thing is a question of code complexity,
not one of scoping.
Michael.
next prev parent reply other threads:[~2023-01-19 13:32 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
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 [this message]
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=87zgae8xav.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).