[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Knowing where a function has been used (bis) [Was: Re: Optimising El
From: |
Emanuel Berg |
Subject: |
Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code] |
Date: |
Tue, 09 Oct 2018 08:35:36 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
Barry Margolin wrote:
> Inline coding is likely to be the LEAST
> effective way to improve performance, except
> for the simplest functions.
If we are talking my personal Elisp - of
course! It will rather be like having an impact
driver in my tool box - it is a good feeling to
have and to understand, but will it improve my
life quality in terms of its functionality,
which obviously is the reason for its
existence? Probably not or at least
very rarely!
If we are talking the insanely long functions
of Gnus, if the funcall overhead is the reason
for that, I don't see why modularization plus
inlining couldn't be one puzzle piece of
the remedy.
--
underground experts united
http://user.it.uu.se/~embe8573
- Re: Optimising Elisp code [again], (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], 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 <=
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Barry Margolin, 2018/10/10
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/10
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Barry Margolin, 2018/10/11
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/11
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Barry Margolin, 2018/10/12
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Eric Abrahamsen, 2018/10/12
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/13
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], tomas, 2018/10/14
- Message not available
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], Emanuel Berg, 2018/10/14
- Re: Knowing where a function has been used (bis) [Was: Re: Optimising Elisp code], tomas, 2018/10/15