From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>, 59057@debbugs.gnu.org
Subject: bug#59057: Emacs 29. Byte compiler sometimes forgets about a defvar.
Date: Thu, 24 Nov 2022 15:36:17 -0500 [thread overview]
Message-ID: <jwvk03kks71.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkm=z8STfz5abAUc-Y72z-cH_XwDxvKwi9qGWDnhTcxxOEw@mail.gmail.com> (Stefan Kangas's message of "Thu, 24 Nov 2022 11:29:32 -0800")
> I guess defvar will have to stay as it is. But would it make sense to
> add a new `declare-variable' function, and then document the form
>
> (defvar <foo>)
>
> to be considered deprecated?
I don't see any concrete benefit. It's only a problem of documentation
and/or teaching programmers. If we could go back to 1984 maybe it would
be worth it to make a different decision, but the cost of the change
doesn't seem worth the very minor (and hypothetical) benefit.
Stefan
next prev parent reply other threads:[~2022-11-24 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 18:46 bug#59057: Emacs 29. Byte compiler sometimes forgets about a defvar Alan Mackenzie
2022-11-07 13:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-07 20:20 ` Alan Mackenzie
2022-11-07 21:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-08 11:01 ` Alan Mackenzie
2022-11-08 14:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-07 21:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-09 13:40 ` Alan Mackenzie
2022-11-09 17:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-24 19:29 ` Stefan Kangas
2022-11-24 19:33 ` Eli Zaretskii
2022-11-24 20:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-11-24 21:12 ` Stefan Kangas
2022-11-25 10:36 ` Alan Mackenzie
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=jwvk03kks71.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=59057@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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.