unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.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 15:36:22 +0100	[thread overview]
Message-ID: <878slwgbvd.fsf@gnus.org> (raw)
In-Reply-To: <jwvh80los0n.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 24 Jan 2020 09:22:49 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> 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).

Reading the fix for the compilation problem, it was:

-    (search-forward "\n;;; This file uses")

It's quite possible that I misunderstand the patch, but doesn't this
mean that (until a couple of days ago), Emacs assumed that that string
exists in .elc files unconditionally.  And now it does, so if you try to
use an Emacs from last week to load .elc files from this week, that
week-old Emacs will break?

That doesn't seem optimal.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-01-24 14:36 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878slwgbvd.fsf@gnus.org \
    --to=larsi@gnus.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).