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: closure within closure, incorrect (?) byte-compiler warnings
Date: Wed, 03 Nov 2021 04:05:46 +0100 [thread overview]
Message-ID: <87o872rl9x.fsf@zoho.eu> (raw)
In-Reply-To: jwvee80f4e4.fsf-monnier+emacs@gnu.org
Stefan Monnier via Users list for the GNU Emacs text editor wrote:
>> (let ((next 1))
>> (defun australian-survivor (ep)
>> (interactive (list (read-number prompt next)))
>
> IIRC the current compiler code doesn't support this kind of
> "interactive spec nested within a lexical scope".
I did a little experiment (last) and the byte compiler
complains when there is a closure within a closure, now it
just gives the "reference to free variable" and not the
"Unused lexical variable" warning I got last time [1] -
I don't know why, but it's still not true ... no complains
when there is just a closure with `interactive'.
> Your code makes sense, but AFAIK it may not always work
> correctly :-(
You mean its worse than just the incorrect message?
Will it work when just evaluated, not byte-compiled?
And "not always work", how can that be?
> You might want to `M-x report-emacs-bug` (and if so, please
> put me in the `X-Debbugs-Cc:`).
Sure ... soon.
(declare-function set-num nil)
(declare-function set-number nil)
(declare-function get-num nil)
(let ((number 0))
(defun set-num (num)
(interactive "nNumber: ")
(setq number num) )
(defun set-number (&optional num)
(interactive (list (read-number "Number: " 0)))
(set-num num) )
(defun get-num ()
(interactive)
(message "%f" number) ))
(declare-function set-num-x nil)
(declare-function set-number-x nil)
(declare-function get-num-x nil)
(let ((caption "Number-X: "))
(let ((number-x 0))
(defun set-num-x (num-x)
(interactive "nNumber-X: ")
(setq number-x num-x) )
(defun set-number-x (&optional num-x)
(interactive (list (read-number caption 0)))
(set-num-x num-x) )
(defun get-num-x ()
(interactive)
(message "%s%f" caption number-x) )))
;; geh.el:43:39: Warning: reference to free variable ‘caption’
[1] https://dataswamp.org/~incal/emacs-init/w3m/w3m-survivor.el
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-11-03 3:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 7:06 closure within closure, incorrect (?) byte-compiler warnings Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-01 7:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-01 12:31 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-03 3:05 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-11-08 23:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-08 23:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-09 0:04 ` Michael Heerdegen
2021-11-09 0:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-10 4:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=87o872rl9x.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).