[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: |
Tue, 09 Oct 2018 10:07:00 +0200 |
User-agent: |
Gnus (5.13), GNU Emacs 25.1.1 (i686-pc-linux-gnu) |
On 2018-10-09 at 08:26, Emanuel Berg wrote:
> Barry Margolin wrote:
>
>> Since we're talking about a byte-code interpreter, not machine code,
>> the pipeline is probably not relevant.
>
> Cannot one have a three-layer architecture, C, compiled Lisp,
> interpretated Lisp?
It’s already like this… or what are you talking about otherwise? We got
C, which interprets directly both byte-compiled and interpreted lisp,
which is all the high-level stuff.
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], (continued)
- 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], Stefan Monnier, 2018/10/07
- Message not available
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/07
- Re: Optimising Elisp code [again], Garreau, Alexandre, 2018/10/07
- Message not available
- Re: Optimising Elisp code [again], Emanuel Berg, 2018/10/08
- 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 <=
- 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, 2018/10/10
- 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