From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: Source file '.../killer-source.el' newer than byte-compiled file Date: Tue, 23 Apr 2019 20:32:45 +0200 Message-ID: <86lg00h8s2.fsf@zoho.eu> References: <8636m8ipt5.fsf@zoho.eu> <8336m84no5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="155336"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Apr 23 20:33:22 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hJ0EL-000eGP-Df for geh-help-gnu-emacs@m.gmane.org; Tue, 23 Apr 2019 20:33:21 +0200 Original-Received: from localhost ([127.0.0.1]:58008 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJ0EK-0005hw-DX for geh-help-gnu-emacs@m.gmane.org; Tue, 23 Apr 2019 14:33:20 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:34076) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hJ0Dy-0005gQ-PG for help-gnu-emacs@gnu.org; Tue, 23 Apr 2019 14:33:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hJ0Dx-0003pT-Dn for help-gnu-emacs@gnu.org; Tue, 23 Apr 2019 14:32:58 -0400 Original-Received: from [195.159.176.226] (port=54314 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hJ0Du-0003h4-8m for help-gnu-emacs@gnu.org; Tue, 23 Apr 2019 14:32:55 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hJ0Dr-000dXb-AY for help-gnu-emacs@gnu.org; Tue, 23 Apr 2019 20:32:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never Cancel-Lock: sha1:ZsR5j6bA5rQmvHiIm++fmmks7HI= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120039 Archived-At: 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 http://user.it.uu.se/~embe8573