From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 39233@debbugs.gnu.org, stefan@marxist.se
Subject: bug#39233: .elc file - possibly outdated backward compatibility comments
Date: Fri, 24 Jan 2020 14:19:08 -0500 [thread overview]
Message-ID: <d8a76cacib.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvd0b83day.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 24 Jan 2020 13:45:34 -0500")
Stefan Monnier wrote:
> + (format "(if (< emacs-major-version %d)\n"
> + ;; Let's allow silently loading into Emacs-27
> + ;; files compiled with Emacs-28.0.NN since the two can
> + ;; be almost identical (e.g. right after cutting the
> + ;; release branch) and people running the development
> + ;; branch can be presumed to know that it's risky anyway.
> + (if (zerop emacs-minor-version)
> + (1- emacs-major-version) emacs-major-version))
> + (format " (message \"BEWARE: %%S was compiled by a more recent version of Emacs (%s)\" #$))" emacs-version)
> + "\n\n"))))
This looks like an unsuppressible warning using a non-standard format
("BEWARE"), hard-coded into the elc?
I had thought you would be doing this in lread.c, behind an option,
similar to the existing load_dangerous_libraries.
I guess the advantage (...) of your version is that it will have an
immediate effect in pre-existing Emacs versions.
next prev parent reply other threads:[~2020-01-24 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 8:44 bug#39233: .elc file - possibly outdated backward compatibility comments Stefan Kangas
2020-01-22 17:13 ` Eli Zaretskii
2020-01-23 16:26 ` Stefan Monnier
2020-01-24 9:20 ` Eli Zaretskii
2020-01-24 14:22 ` Stefan Monnier
2020-01-24 14:36 ` Lars Ingebrigtsen
2020-01-24 16:08 ` Stefan Kangas
2020-01-24 15:23 ` Eli Zaretskii
2020-01-24 17:29 ` Stefan Monnier
2020-01-24 18:45 ` Stefan Monnier
2020-01-24 19:06 ` Stefan Kangas
2020-01-24 19:14 ` Stefan Monnier
2020-01-24 19:19 ` Glenn Morris [this message]
2020-01-24 20:08 ` Eli Zaretskii
2020-09-21 12:56 ` Lars Ingebrigtsen
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=d8a76cacib.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=39233@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--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.