From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Re: Lexical vs. dynamic: small examples?
Date: Sun, 15 Aug 2021 06:44:28 +0200 [thread overview]
Message-ID: <87pmufs4er.fsf@zoho.eu> (raw)
In-Reply-To: 87y293sdxk.fsf@zoho.eu
Drew Adams wrote, somewhere else:
> If this is only about let "let's" have two lets, one
> "let-stay" and one "let-follow".
`let' is not the only construct that can define a
scope. For example, a function definition (a `defun'
or a lambda) defines the scope of its formal
parameters - they're lexically scoped.
Yes, and what happens is, the formal parameters are check
first, only after that are global variables checked!
But that is completely normal and 100% expected. If that is
"lexical scope", how would one do it in another way? (OK, it
_is_ lexical binding for the arguments and dynamic for the
globals but has this any practical implications?)
No, the only thing I've seen so far - maybe the only thing it
is? - is `let', and that acts in two ways, the lexical way if
one puts
;;; -*- lexical-binding: t -*-
first thing in the source file, and if one doesn't, it acts in
the dynamic way.
So I wonder again, why not just have two let, one "let-stay"
(the variables stay so has to be used and/or passed
explicitely), and "let-follow" (the variables follow
everywhere the code goes within the let form).
Then one could drop this whole discussion because everything
would work as expected and everyone could use whatever they
wanted and instead of explaining some scope vs another in
terms of theory one would have one docstring for "let-stay"
and one for "let-follow" and these would also not confuse
anything by engaging in a theoretical discussion but just
describe what the function does and what its purpose is.
?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-08-15 4:44 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 3:34 Lexical vs. dynamic: small examples? Eduardo Ochs
2021-08-14 3:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 4:12 ` Eduardo Ochs
2021-08-14 7:35 ` tomas
2021-08-14 16:00 ` Eduardo Ochs
2021-08-14 19:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:42 ` tomas
2021-08-14 19:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:31 ` tomas
2021-08-14 21:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 21:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 13:35 ` [External] : " Drew Adams
2021-08-14 16:15 ` Eduardo Ochs
2021-08-14 19:00 ` Gregory Heytings
2021-08-14 20:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:23 ` Gregory Heytings
2021-08-14 21:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 21:13 ` tomas
2021-08-14 21:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 20:41 ` tomas
2021-08-15 0:29 ` [External] : " Drew Adams
2021-08-15 0:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 1:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 1:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 4:44 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-08-15 5:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 15:49 ` Drew Adams
2021-08-15 18:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 21:55 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-15 22:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 21:57 ` Drew Adams
2021-08-15 22:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:54 ` Drew Adams
2021-08-15 23:16 ` Drew Adams
2022-01-09 7:08 ` Jean Louis
2022-01-09 15:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 23:42 ` Arthur Miller
2021-08-15 22:02 ` Lars Ingebrigtsen
2021-08-15 22:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:44 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-21 3:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-24 2:08 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-25 23:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-25 23:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-26 0:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-26 0:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-26 17:01 ` FW: " Drew Adams
2021-08-26 23:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-25 23:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-25 23:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-26 0:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-28 1:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-28 1:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 22:58 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-15 23:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 23:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-08-16 0:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-15 15:42 ` FW: " Drew Adams
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=87pmufs4er.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).