[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Optimising Elisp code [again]
From: |
Garreau, Alexandre |
Subject: |
Re: Optimising Elisp code [again] |
Date: |
Thu, 11 Oct 2018 01:54:17 +0200 |
User-agent: |
Gnus (5.13), GNU Emacs 25.1.1 (i686-pc-linux-gnu) |
On 2018-10-10 at 12:18, Barry Margolin wrote:
> In article <86ftxfm98q.fsf@zoho.com>, Emanuel Berg <moasen@zoho.com>
> wrote:
>> I mean, compile the Lisp that isn't user
>> defined and unlikely to change - compile for
>> real, not byte-compile for
>> sped-up interpretation.
>>
>> I.e.: fun-and-play Elisp on the top
>> compiled Elisp in the middle
>> C downmost
>>
>> ?
>
> The Elisp interpreter is probably tightly intertwined with the Emacs
> editor code. Disentangling them so you can compile Elisp to machine code
> would be a big project, and probably not worth it.
Why would that need distangling? Couldn’t editor code be compiled as
well? I understand things need to stay dynamic and redefinable, but a
large portion would remain unchanged anyway for most of time and the
things that would most likely be changed would be less stable and
less low-level things that wouldn’t break other stuff wouldn’t it?
- Re: Optimising Elisp code [again], (continued)
- Re: Optimising Elisp code [again], tomas, 2018/10/08
- Message not available
- Re: Optimising Elisp code [again], Barry Margolin, 2018/10/08
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/09
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/09
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/09
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/09
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/09
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/09
- Re: Optimising Elisp code [again], Barry Margolin, 2018/10/10
- Re: Optimising Elisp code [again], Óscar Fuentes, 2018/10/10
- Re: Optimising Elisp code [again],
Garreau, Alexandre <=
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/11
- Re: Optimising Elisp code [again], Robert Thorpe, 2018/10/12
- Message not available
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/07
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Garreau, Alexandre, 2018/10/07
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Barry Margolin, 2018/10/07
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/08
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Garreau, Alexandre, 2018/10/08
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/08
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Barry Margolin, 2018/10/08
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/09