[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Optimising Elisp code
From: |
tomas |
Subject: |
Re: Optimising Elisp code |
Date: |
Fri, 5 Oct 2018 12:03:08 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, Oct 04, 2018 at 07:15:30PM -0700, Davin Pearson wrote:
> Suppose that you have a function:
>
> (defun foo ()
> (bar))
>
> And bar is a function that has no side effects and returns 123 then calling
> the function code-optimize (the name of my optimisation routine)
>
> M-x code-optimize on the function foo will result in the following defun
>
> (defun foo ()
> 123)
Have you already looked at the code produced by the elisp compiler? As
in doing "compile-function" and "disassemble-function"?
Have you had a look at eval-and-compile and friends?
Perhaps elisp is already doing (parts of) what you have in mind?
Cheers
-- tomás
signature.asc
Description: Digital signature
- Optimising Elisp code, Davin Pearson, 2018/10/04
- Re: Optimising Elisp code, Davin Pearson, 2018/10/04
- Re: Optimising Elisp code,
tomas <=
- Re: Optimising Elisp code, Barry Margolin, 2018/10/05
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, Óscar Fuentes, 2018/10/05
- Message not available
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, Óscar Fuentes, 2018/10/05
- Message not available
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05