From: Jens Schmidt via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>,
"Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 66136@debbugs.gnu.org
Subject: bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment
Date: Sat, 23 Sep 2023 00:41:14 +0200 [thread overview]
Message-ID: <87v8c14yr9.fsf@sappc2.fritz.box> (raw)
In-Reply-To: <jwv4jjlgaab.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 22 Sep 2023 17:39:35 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I know Mattias played with this part of the code (mostly to try and
> figure what to do about the ordering of the various possible kinds of
> declarations, which is a related yet different issue). Maybe he has
> a more informed opinion.
One more data point for opinion building: When byte-compiling a
completely empty function (no declarations, no body forms):
------------------------- snip -------------------------
(let ((lexical-binding t))
(byte-compile
'(defun foo (arg))))
------------------------- snip -------------------------
some upper layer already seems to replace the empty body by a sole nil,
which is then kept by function `macroexp-parse-body':
-------------------- *trace-output --------------------
1 -> (macroexp-parse-body (nil))
1 <- macroexp-parse-body: (nil nil)
-------------------- *trace-output --------------------
So probably we should mimic that in `macroexp-parse-body' if there are
declarations, but no body forms? Or change that upper layer to also add
a sole nil in the declarations-only case?
next prev parent reply other threads:[~2023-09-22 22:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 10:44 bug#66136: 29.1; byte-compiler reports "misplaced interactive spec" with empty fct in lexical environment Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 20:20 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-21 21:39 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 5:58 ` Eli Zaretskii
2023-09-22 14:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 21:26 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 21:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 22:41 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-23 10:46 ` Mattias Engdegård
2023-09-23 16:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-23 16:43 ` Mattias Engdegård
2023-09-23 19:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 10:42 ` Mattias Engdegård
2023-09-24 15:42 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-23 19:19 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-23 22:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 10:24 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25 13:22 ` Mattias Engdegård
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=87v8c14yr9.fsf@sappc2.fritz.box \
--to=bug-gnu-emacs@gnu.org \
--cc=66136@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).