unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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: Tue, 09 Nov 2021 00:09:33 +0100	[thread overview]
Message-ID: <87sfw62qj6.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".
>
> Your code makes sense, but AFAIK it may not always work correctly :-(

Indeed, it doesn't work after a restart when the byte-compiled
code (.elc) is loaded.

It causes no crash or error message until you use the
function, then it says

  call-interactively: Symbol’s value as variable is void:
  prompt

> You might want to `M-x report-emacs-bug` (and if so, please
> put me in the `X-Debbugs-Cc:`).

OK, I hope to do that soon ...

;;; -*- lexical-binding: t -*-
;;;
;;; this file:
;;;   https://dataswamp.org/~incal/emacs-init/w3m/w3m-survivor.el

(require 'w3m-search)
(require 'cl-lib)

(declare-function australian-survivor nil)
(declare-function us-survivor         nil)

(let ((opts   "torrent 1080p")
      (show   "Survivor")
      (prompt "episode: ") )
  (let ((next 1))
    (defun australian-survivor (ep)
      (interactive (list (read-number prompt next)))
      (w3m-search
       w3m-search-default-engine
       (format "s08e%02d Australian %s %s" ep show opts) )
      (setq next (1+ ep)) ))
  (defalias 'aus #'australian-survivor)

  (let ((next 1))
    (defun us-survivor (ep)
      (interactive (list (read-number prompt next)))
      (w3m-search
       w3m-search-default-engine
       (format "s41%02d %s %s" ep show opts) )
      (setq next (1+ ep)) ))
  (defalias 'us #'us-survivor) )

;; In toplevel form:
;; w3m/w3m-survivor.el:12:1: Warning: Unused lexical variable `prompt'
;; w3m/w3m-survivor.el:12:1: Warning: Unused lexical variable `next'
;; w3m/w3m-survivor.el:26:39: Warning: reference to free variable ‘prompt’
;; w3m/w3m-survivor.el:26:46: Warning: reference to free variable ‘next’
;; w3m/w3m-survivor.el:22:14: Warning: Unused lexical variable `next'

-- 
underground experts united
https://dataswamp.org/~incal




  parent reply	other threads:[~2021-11-08 23:09 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
2021-11-08 23:09   ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
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=87sfw62qj6.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).