unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Warning on files byte-compiled with different versions
Date: Sun, 14 Feb 2016 16:02:29 +0100	[thread overview]
Message-ID: <87a8n39vy2.fsf@linux-m68k.org> (raw)
In-Reply-To: <jwv7fi78kb4.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Sun, 14 Feb 2016 09:00:56 -0500")

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

>> So, the answer is no, AFAICT. Second question, is there any reason why
>> this kind of functionality could not be added?
>
> Indeed.  The byte-compiler could simply emit
>
>    `(if (< emacs-major-version ,emacs-major-version)
>         (message "This file was compiled for a more recent Emacs"))
>
> at the beginning of every file.  IIRC we used to do something like that.

We have the bytecode version encoded in the header, and a check if it
contains multi-byte characters.  Just because the file was compiled by a
later version should not be a reason to prevent loading it, only if the
format itself changes.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2016-02-14 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 14:08 Warning on files byte-compiled with different versions Phillip Lord
2016-02-12 14:09 ` Phillip Lord
2016-02-14 14:00   ` Stefan Monnier
2016-02-14 15:02     ` Andreas Schwab [this message]
2016-02-14 17:15       ` Stefan Monnier
2016-02-14 17:29         ` Andreas Schwab
2016-02-20  2:29     ` John Wiegley

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=87a8n39vy2.fsf@linux-m68k.org \
    --to=schwab@linux-m68k.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).