[Top][All Lists]

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

Re: Add a configure option for NATIVE_FULL_AOT?

From: tomas
Subject: Re: Add a configure option for NATIVE_FULL_AOT?
Date: Wed, 18 Aug 2021 18:34:55 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Aug 18, 2021 at 07:26:57PM +0300, Eli Zaretskii wrote:
> > Date: Wed, 18 Aug 2021 18:22:16 +0200
> > From: tomas@tuxteam.de
> > Cc: emacs-devel@gnu.org
> > 
> > When the user wants to change a distribution-specific .el, the default
> > way to do it would be to make a user-writable copy somewhere in a
> > user-controlled directory (ISTR there was a mechanism doing this
> > semi-transparently, but I may be confused). If `load-path' is set up
> > correctly, the user's variant takes precedence. Same would go for
> > .eln files resp. native-comp-eln-load-path, right?
> Nominally, yes.  But then you have 2 copies of the same .eln file, in
> 2 different places.

They would be different, one of them from an .el with user changes.

>                     That's got to confuse people and perhaps create
> hard-to-debug situations where Emacs behaves erratically.
> > > We actually do use native-comp-eln-load-path to also decide where to
> > > store the *.eln files, but that uses a simplistic heuristic that
> > > treats the last element of the list specially.  The heuristic is
> > > hard-coded in several places, so not easily overridden.
> > 
> > Oh, the /last/ element, i.e. the one with the least precedence is the
> > one where .eln files are stored? There goes my house of cards.
> > Interesting ;-)
> The preloaded *.eln files are stored there, yes.

But why on the "least precedence" slot, i.e. in the place at the
list's tail? I'd have expected them to be stored in the place
at the list's head.

>                                                  How else would you
> arrange for them to be of the least precedence, when lists are
> generally searched head to tail?

Why would I want to arrange "them" [1] to be of the least precedence?
A freshly user-compiled file should have the highest precedence, IMO.

You see: those are the interesting details I've not yet digested, it
seems :-)

[1] provided our "them" refers to the same thing: "the .eln files
   freshly compiled in the user's behalf, because Emacs has seen
   an .el(c) file it had not seen before"

 - t

Attachment: signature.asc
Description: Digital signature

reply via email to

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