Re: On elisp running native

[Andrea Corallo]

Stefan Monnier <address@hidden> writes:

> I think the focus should be on:
> - making it work everywhere
> - making it easy/convenient to use (e.g. even if you share your $HOME between
>   different architectures or even different OSes as well as different
>   versions of Emacs)

I think the natural action would be to move the eln in the build
directory (as these are in fact compiled).  Unfortunately this would not
work with the elpa packages...  The other option would be to add a
suffix to the the eln file but is not nice at all.  Any idea?

Consider that now the situation is pretty bad because eln are likely not
to be compatible even from different builds on the same codebase with
different configure parameters.

> As far as I'm concerned, support for a nil value of lexical-binding is
> a non-goal (it should still work, of course, e.g. by using the
> bytecode): the dynbind version of Elisp is a legacy language and it's
> better to update the code to lexbind than to try and make that legacy
> code run faster.

Good I agree, and even if not that hard would be something more to care
about.

-- 
address@hidden