[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Optimising Elisp code
From: |
Emanuel Berg |
Subject: |
Re: Optimising Elisp code |
Date: |
Fri, 05 Oct 2018 21:14:02 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
> I have now look it up in another book, namely
>
> @book{c-programming-language,
> author = {Bjarne Stroustrup},
> ISBN = {0-201-53992-6},
> publisher = {Addison Wesley},
> title = {The C++ Programming Language},
> year = 1992
> }
>
> here it says much less, with no attempt to
> explain what actually "inline" means, still, it
> seems to contradict what you say, because it
> says the keyword inline is a "hint to the
> compiler" to generate the code inline rather
> than have the function called the usual way
> (page 124).
I was about to say "I can do this all night",
but then I'd be a lier because I'm running out
of C++ books. This is the last one
@book{small-c-how-to-program,
author = {H M Deitel and P J Deitel},
ISBN = {0-13-185758-4},
publisher = {Pearson},
title = {Small C++ How to Program},
year = 2005
}
and it says virtually the same thing: "inline"
advices the compiler to "generate a copy of the
function's code in place" rather than the usual
call. (It also says the compiler can choose not
to do this; page 246.)
But I'm not saying you are wrong. I was once
~fluent in *writing* C++, but I didn't claim
then, and certainly do not claim now, to
understand what goes on under the hood.
To young, promising programmers, two pieces of
advice:
1) don't be a professional programmer; and
2) stay away from these books:
%%%% C++
@book{small-c-how-to-program,
author = {H M Deitel and P J Deitel},
ISBN = {0-13-185758-4},
publisher = {Pearson},
title = {Small C++ How to Program},
year = 2005
}
@book{c-programming-language,
author = {Bjarne Stroustrup},
ISBN = {0-201-53992-6},
publisher = {Addison Wesley},
title = {The C++ Programming Language},
year = 1992
}
@book{cpp-direkt,
author = {Jan Skansholm},
ISBN = {91-44-47931-X},
publisher = {Studentlitteratur},
title = {C++ direkt},
year = 1996
}
--
underground experts united
http://user.it.uu.se/~embe8573
- Re: Optimising Elisp code, (continued)
- 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, 2018/10/05
- Message not available
- Re: Optimising Elisp code, Emanuel Berg, 2018/10/05
- Re: Optimising Elisp code,
Emanuel Berg <=
- 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
Re: Optimising Elisp code, Stefan Monnier, 2018/10/06