From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Phil Sainty <psainty@orcon.net.nz>,
Lars Ingebrigtsen <larsi@gnus.org>,
58513@debbugs.gnu.org
Subject: bug#58513: describe-function should say that defconst variables are constant
Date: Sat, 15 Oct 2022 10:11:35 -0400 [thread overview]
Message-ID: <jwvsfjpkwsh.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmnfLuEYVvwpVuWXAEiMpWknqxOz2suqcynW42wQzTULWA@mail.gmail.com> (Stefan Kangas's message of "Sat, 15 Oct 2022 12:33:29 +0000")
Stefan Kangas [2022-10-15 12:33:29] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> The byte-compiler already does warn about it, but only if the assignment
>> is in the same file as the `defconst`.
> I don't get any warnings with this recipe:
>
> echo "(defconst foo-bar t) (setq foo-bar nil)" > /tmp/foo.el
> emacs -Q -batch -eval '(byte-compile-file "/tmp/foo.el")'
>
> Am I missing something?
Hmm... I don't get a warning either. And looking at `bytecomp.el` I see
that we push stuff to `byte-compile-const-variables` but we never look
stuff up in it :-(
I'm pretty sure I wrote some code to use that variable (apparently
around 2003), but apparently it got lost in subsequent changes, probably
when we introduced lexical-binding.
Stefan
prev parent reply other threads:[~2022-10-15 14:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 12:04 bug#58513: describe-function should say that defconst variables are constant Stefan Kangas
2022-10-14 12:23 ` Lars Ingebrigtsen
2022-10-14 12:35 ` Phil Sainty
2022-10-14 12:40 ` Lars Ingebrigtsen
2022-10-14 13:03 ` Stefan Kangas
2022-10-14 13:07 ` Lars Ingebrigtsen
2022-10-14 13:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 14:25 ` Lars Ingebrigtsen
2022-10-14 16:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-15 10:04 ` Lars Ingebrigtsen
2022-10-16 20:51 ` Richard Stallman
2022-10-16 21:11 ` Drew Adams
2022-10-17 5:41 ` Stefan Kangas
2022-10-17 10:41 ` Lars Ingebrigtsen
2022-10-15 12:33 ` Stefan Kangas
2022-10-15 14:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvsfjpkwsh.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=58513@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=psainty@orcon.net.nz \
--cc=stefan@marxist.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.