From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Emanuel Berg Newsgroups: gmane.emacs.help Subject: Re: Optimising Elisp code Date: Fri, 05 Oct 2018 21:26:38 +0200 Organization: Aioe.org NNTP Server Message-ID: <861s942o0h.fsf@zoho.com> References: <638fb7dc-6fc5-4645-8793-97a00038a3a8@googlegroups.com> <86r2h44fqg.fsf@zoho.com> <86in2g4eq6.fsf@zoho.com> <86d0so48a6.fsf@zoho.com> <865zyg448j.fsf@zoho.com> <86efd42olh.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1538767707 7468 195.159.176.226 (5 Oct 2018 19:28:27 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 5 Oct 2018 19:28:27 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Oct 05 21:28:23 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1g8Vlt-0001pU-8M for geh-help-gnu-emacs@m.gmane.org; Fri, 05 Oct 2018 21:28:21 +0200 Original-Received: from localhost ([::1]:36670 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8Vnz-0007pf-Jb for geh-help-gnu-emacs@m.gmane.org; Fri, 05 Oct 2018 15:30:31 -0400 X-Received: by 2002:a1c:c90f:: with SMTP id f15-v6mr1338611wmb.0.1538767599693; Fri, 05 Oct 2018 12:26:39 -0700 (PDT) X-FeedAbuse: http://nntpfeed.proxad.net/abuse.pl feeded by 78.192.65.63 Original-Path: usenet.stanford.edu!s185-v6no1304113wmd.0!news-out.google.com!z184-v6ni4083wmz.0!nntp.google.com!feeder1-2.proxad.net!proxad.net!feeder1-1.proxad.net!nntpfeed.proxad.net!news.muarf.org!news.gegeweb.eu!gegeweb.org!aioe.org!.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 37 Original-NNTP-Posting-Host: xQsFb8j6c/kdg9AvIrnVFA.user.gioia.aioe.org Original-X-Complaints-To: abuse@aioe.org Mail-Copies-To: never X-Notice: Filtered by postfilter v. 0.8.3 Cancel-Lock: sha1:pZZ99p0jlBGNNmXNWFmM3P4fIEc= Original-Xref: usenet.stanford.edu gnu.emacs.help:224012 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:118138 Archived-At: > 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 I was wrong, I have yet another one, but not on C++, but on C, namely @book{vägen-till-c, author = {Ulf Bilting and Jan Skansholm}, ISBN = {978-91-44-01468-5}, publisher = {Studentlitteratur}, title = {Vägen till C}, year = 2000 } it says, page 279, that into the "new" C99 standard, from C++, they have brought the "inline" keyword. Then they just say the same thing, instead of a call, the insertion of code. They also say the previous method of getting somewhat the same stuff has been the use of macros. By macros, they mean the #preprocessor replacement of text! So they think the new "inline" is really good! And one can appreciate that :) Now I really need to drink a couple of beers and ride my bike (bicycle). I haven't written this much on gnu.emacs.help in ages. Maybe I'm not getting older after all! That, I'd appreciate as well... -- underground experts united http://user.it.uu.se/~embe8573