From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: the (declare special) declaration with lexical scope.
Date: Sun, 23 Apr 2023 16:22:11 +0200 [thread overview]
Message-ID: <878reiznjg.fsf@dataswamp.org> (raw)
In-Reply-To: m31qkbnq3r.fsf@leonis4.robolove.meer.net
Madhu wrote:
> binding it lexically elsewhere. For example:
>
> (let (_)
> (defvar x) ; Let-bindings of ‘x’ will be dynamic within this let.
> (let ((x -99)) ; This is a dynamic binding of ‘x’.
> (defun get-dynamic-x ()
> x)))
You need this for the byte-compiler:
(declare-function get-dynamic-x nil)
As for your question - that would be a dynamic let-closure and
not a lexical. Interesting. What would the implications be?
And see if you can use `dlet'.
--
underground experts united
https://dataswamp.org/~incal
prev parent reply other threads:[~2023-04-23 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 5:07 the (declare special) declaration with lexical scope Madhu
2023-04-23 9:47 ` Platon Pronko
2023-04-24 2:16 ` Madhu
2023-04-23 14:22 ` Emanuel Berg [this message]
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=878reiznjg.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.
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).