[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Optimising Elisp code
From: |
Óscar Fuentes |
Subject: |
Re: Optimising Elisp code |
Date: |
Fri, 05 Oct 2018 19:46:18 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (gnu/linux) |
Emanuel Berg <moasen@zoho.com> writes:
>> Just in case any bystander finds this post:
>> don't rely on anything that is mentioned
>> above, nor for C++ `inline' keyword nor for
>> code inlining in general.
>
> I read it in this book:
>
> @book{cpp-direkt,
> author = {Jan Skansholm},
> ISBN = {91-44-47931-X},
> publisher = {Studentlitteratur},
> title = {C++ direkt},
> year = {1996}
> }
The key data point there is "1996". But even then things were not as
simple as you described.
Since long time ago C++ "inline" is really about the ODR ("One
Definition Rule"), not about how the compiler generates code.
- Optimising Elisp code, Davin Pearson, 2018/10/04
- Re: Optimising Elisp code, Davin Pearson, 2018/10/04
- Re: Optimising Elisp code, tomas, 2018/10/05
- 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 <=
- 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
- Re: Optimising Elisp code, Stefan Monnier, 2018/10/05
- Message not available
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, James K. Lowden, 2018/10/05
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code, Barry Margolin, 2018/10/06
Knowing where a function has been used (e.g. for optimizing) [Was: Re: Optimising Elisp code], Garreau, Alexandre, 2018/10/06