From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: jixiuf <jixiuf@qq.com>, 45619@debbugs.gnu.org
Subject: bug#45619: 28.0.50; pcase-let on MacOS doesn't work
Date: Fri, 08 Jan 2021 17:13:18 -0500 [thread overview]
Message-ID: <jwv1revgjtm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878s936voy.fsf@web.de> (Michael Heerdegen's message of "Fri, 08 Jan 2021 21:05:33 +0100")
> I wondered what happens when a pcase form binds a symbol S that is not
> defined at compile time (normal case) but then a user loads a package
> that declares S as (globally) special. Then that pcase binding gets
> dynamical scope at runtime (as it would happen with any `let' binding),
> right? Sorry if this is silly or trivial, I was just wondering...
This is a much more general problem which affects all variable bindings
rather than only those of `pcase`.
Note that the choice between dynamic and lexical scoping is made at
compile-time (when you compile the code), so if the code is compiled you
should be somewhat immune to the problem.
Stefan
next prev parent reply other threads:[~2021-01-08 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 7:59 bug#45619: 28.0.50; pcase-let on MacOS doesn't work jixiuf
2021-01-04 12:44 ` Michael Heerdegen
2021-01-04 15:41 ` Drew Adams
2021-01-04 17:41 ` Stefan Monnier
2021-01-04 19:50 ` Michael Heerdegen
2021-01-04 20:37 ` Stefan Monnier
2021-01-04 22:08 ` Michael Heerdegen
2021-01-05 2:06 ` Stefan Monnier
2021-01-07 11:38 ` Michael Heerdegen
2021-01-07 15:19 ` Stefan Monnier
2021-01-08 20:05 ` Michael Heerdegen
2021-01-08 22:13 ` Stefan Monnier [this message]
2022-02-12 7:46 ` Lars Ingebrigtsen
2022-02-12 14:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 16:30 ` Lars Ingebrigtsen
2022-02-12 17:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 17:21 ` Lars Ingebrigtsen
2022-02-12 22:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwv1revgjtm.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=45619@debbugs.gnu.org \
--cc=jixiuf@qq.com \
--cc=michael_heerdegen@web.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).