From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Source file '.../killer-source.el' newer than byte-compiled file
Date: Tue, 23 Apr 2019 22:02:36 +0300 [thread overview]
Message-ID: <831s1s4kab.fsf@gnu.org> (raw)
In-Reply-To: <86lg00h8s2.fsf@zoho.eu> (message from Emanuel Berg on Tue, 23 Apr 2019 20:32:45 +0200)
> From: Emanuel Berg <moasenwood@zoho.eu>
> Date: Tue, 23 Apr 2019 20:32:45 +0200
>
> Eli Zaretskii wrote:
>
> > Its purpose is to tell you that Emacs loads
> > a .elc file that is older than the
> > corresponding .el file.
> > See load-prefer-newer.
>
> OK, so I should have that `t'!
If you really want that. Personally, I'm not sure.
> Is there a downside to this, assuming the
> latest version is always the better, and b.elc
> *is* compiled eventually?
That assumption might be false. For example, you may be working on
a.el, and it might have bugs.
> If there is a downside, i.e. it _is_ better to
> load the byte-compiled code (assuming it to be
> newer than the source), what should one do?
Just ignore those messages, really. They are mostly harmless. You
could compile the dependent file again if you want, but that is rarely
needed, mainly when they define macros that were changed, and those
macros are used by the files which require a.el.
next prev parent reply other threads:[~2019-04-23 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 17:39 Source file '.../killer-source.el' newer than byte-compiled file Emanuel Berg
2019-04-23 17:49 ` Eli Zaretskii
2019-04-23 18:32 ` Emanuel Berg
2019-04-23 18:39 ` Emanuel Berg
2019-04-23 19:03 ` Eli Zaretskii
2019-04-23 22:42 ` Emanuel Berg
2019-04-23 23:17 ` Nick Dokos
2019-04-24 0:18 ` Emanuel Berg
2019-04-24 1:33 ` Emanuel Berg
2019-04-24 6:24 ` Eli Zaretskii
2019-04-25 3:25 ` `eval-when-compile' and circular dependencies (was: Re: Source file '.../killer-source.el' newer than byte-compiled file) Emanuel Berg
2019-04-25 6:37 ` Eli Zaretskii
2019-04-25 7:03 ` Emanuel Berg
2019-04-25 8:43 ` Eli Zaretskii
2019-04-23 19:02 ` Eli Zaretskii [this message]
2019-04-23 22:59 ` Source file '.../killer-source.el' newer than byte-compiled file Emanuel Berg
2019-04-23 18:02 ` Emanuel Berg
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=831s1s4kab.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).