From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: christopher@librehacker.com, drew.adams@oracle.com,
74261@debbugs.gnu.org
Subject: bug#74261: 30.0.92; Remove modeline warning for explicit uses of dynamic binding
Date: Mon, 25 Nov 2024 14:20:20 +0200 [thread overview]
Message-ID: <86ldx7ijy3.fsf@gnu.org> (raw)
In-Reply-To: <E1tFQle-0006pV-I4@fencepost.gnu.org> (message from Richard Stallman on Sun, 24 Nov 2024 23:32:10 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: drew.adams@oracle.com, christopher@librehacker.com,
> 74261@debbugs.gnu.org
> Date: Sun, 24 Nov 2024 23:32:10 -0500
>
> > > So I think that the indicator that this file uses dynamic binding
> > > ought to be somewhat loud, so that users won't overlook it.
>
> > I tend to agree, but only if the file does not already have a
> > lexical-binding cookie which makes the file use dynamical binding.
>
> Are you assuming that the person looking at the file
> is also the file's author? In that situation, I would agree:
> you don't need to be warned that your file is set to use
> dynamic binding if you set it that way yourself.
>
> But I think it is useful to show this warning when person A looks at
> person B's file. Person A is likely to assume the file use lexical
> binding, when just about all files do so; therefore, it is useful to
> inform A that this file makes the unusual choice.
That could be the case, yes.
However, another way of looking at such situation is that if the
author (person B) decided the file should use dynamic scoping, that's
"good enough" for person A. For example, assume that person B is
Emacs maintainers, and the file is part of Emacs.
I guess which POV is taken depends on whether person A is about to
hack on the file, or wants a seep understanding of its workings, or is
just reading the code?
next prev parent reply other threads:[~2024-11-25 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:33 bug#74261: 30.0.92; Remove modeline warning for explicit uses of dynamic binding Christopher Howard
2024-11-08 18:05 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-11 5:13 ` Richard Stallman
2024-11-11 12:26 ` Eli Zaretskii
2024-11-25 4:32 ` Richard Stallman
2024-11-25 12:20 ` Eli Zaretskii [this message]
2024-11-28 4:54 ` Richard Stallman
2024-11-28 9:40 ` Eli Zaretskii
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=86ldx7ijy3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74261@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=drew.adams@oracle.com \
--cc=rms@gnu.org \
/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.