[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Source file '.../killer-source.el' newer than byte-compiled file

From: Emanuel Berg
Subject: Re: Source file '.../killer-source.el' newer than byte-compiled file
Date: Tue, 23 Apr 2019 20:32:45 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

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'!

But if so, sometimes the b.el and not the b.elc
will be `require'd by a.el->a.elc (whichever is
correct to say does the the requiring - a.el?).

Is there a downside to this, assuming the
latest version is always the better, and b.elc
*is* compiled eventually?

>> Has it to do with files being `require'd
>> before compilation has gotten that far?
>> So if a.el is compiled into a.elc, but
>> a requires b, only at that time b.elc hasn't
>> been compiled *but* b.el has been edited?
> Yes.

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?
touch(1) a.el and byte-compile again?
Because then, there should be no problem with
b.elc being out of date! If this is correct,
perhaps the byte-compiler should tell what file
has the problem to begin with?

Or even not do anything about it (a.el), and
then one would simply compile twice? Hm, maybe
this can get messy if one have lots to
require... - but as long as they are not
circular it should work out fine, right?

underground experts united

reply via email to

[Prev in Thread] Current Thread [Next in Thread]