From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Effect of lexical binding upon function paramaters
Date: Sat, 05 Nov 2022 16:32:41 +0100 [thread overview]
Message-ID: <87o7tlfmcm.fsf@dataswamp.org> (raw)
In-Reply-To: jwvcza2v7q8.fsf-monnier+emacs@gnu.org
Stefan Monnier via Users list for the GNU Emacs text editor wrote:
>> What I can see from this test below, formal parameters
>> ("arguments" in standard information interchange) are
>> always dynamic under dynabound, and always static under
>> lexical
>
> Yup. Same holds for the var bound by `condition-case`.
> The binding constructs that can be "either/or" are `let` and
> `let*` (via `lexical-let` for the dynbound dialect and via
> `defvar` for the lexbound dialect).
For dynbound `let'/`let*' defaults to dynamic, just as it
defaults to lexical for lexbound.
However in the presence of another variable with the same
name, while `let'/`let*' can bind it to another value, it
doesn't change the lexical/dynamic status of the variable -
and this is the case for both dialects.
So how do you create a lexical binding under dynbound?
`lexical-let'. (See example last.) And a dynamic/special
variable under lexbound? `defvar'.
So is it all about what let/let* defaults to? Almost?
The other cases (formal parameters etc), should one consider
them being dynamic as just collateral damage from an
implementation policy detail which had to do with something
else or are there arguments (ha) for that as well?
(defun test-y ()
y)
(let ((y 1))
(test-y) ) ; works, y is dynamic
(lexical-let ((y 6))
(let ((y 10))
y ; 10 but ...
(test-y) )) ; DNC in test-y, y is lexical
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-11-05 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 11:01 Effect of lexical binding upon function paramaters Heime
2022-11-03 13:01 ` Emanuel Berg
2022-11-04 19:30 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-04 20:23 ` Heime
2022-11-04 20:34 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-04 20:45 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-05 16:25 ` Emanuel Berg
2022-11-05 15:32 ` Emanuel Berg [this message]
2022-11-06 20:44 ` Emanuel Berg
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=87o7tlfmcm.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.