From: Eli Zaretskii <eliz@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 17:23:27 +0200 [thread overview]
Message-ID: <83v9p0ri8g.fsf@gnu.org> (raw)
In-Reply-To: <jwvh80los0n.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 24 Jan 2020 09:22:49 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: stefan@marxist.se, 39233@debbugs.gnu.org
> Date: Fri, 24 Jan 2020 09:22:49 -0500
>
> > Will these changes still allow old Emacs binaries to load *.elc files
> > compiled by Emacs after these changes?
>
> New Emacsen loading old .elc won't be affected.
>
> Old Emacsen loading .elc files compiled by new Emacsen is something that
> has always been risky, tho it has sometimes worked. My proposal is to
> make it emit a warning (so it will work as much as it does now, but
> will bring to the attention of the user that it's in murky territory).
A warning is a (minor) annoyance. Maybe someone will be annoyed
enough to complain (we shall see), but for the use cases I need this
-- which is running old Emacs binaries to quickly bisect bugs in C
code or in preloaded Lisp -- this doesn't sound like a terrible
problem. As long as this use case works as well (or as badly) as it
did before, modulo the warning.
I feared that this won't work at all, because the *.elc files lack
something which old Emacs binaries will look for at load time.
Thanks.
next prev parent reply other threads:[~2020-01-24 15:23 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 [this message]
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
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=83v9p0ri8g.fsf@gnu.org \
--to=eliz@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.