From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: Optimising Elisp code Date: Fri, 05 Oct 2018 19:46:18 +0200 Message-ID: <87woqwe179.fsf@telefonica.net> References: <638fb7dc-6fc5-4645-8793-97a00038a3a8@googlegroups.com> <86r2h44fqg.fsf@zoho.com> <86in2g4eq6.fsf@zoho.com> <86d0so48a6.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1538762059 24660 195.159.176.226 (5 Oct 2018 17:54:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 5 Oct 2018 17:54:19 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (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 19:54:15 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 1g8UIk-0006Db-Te for geh-help-gnu-emacs@m.gmane.org; Fri, 05 Oct 2018 19:54:11 +0200 Original-Received: from localhost ([::1]:36336 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8UKr-0002dR-7J for geh-help-gnu-emacs@m.gmane.org; Fri, 05 Oct 2018 13:56:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35449) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8UIl-00013U-Hp for help-gnu-emacs@gnu.org; Fri, 05 Oct 2018 13:54:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g8UBO-0004A4-HL for help-gnu-emacs@gnu.org; Fri, 05 Oct 2018 13:46:38 -0400 Original-Received: from [195.159.176.226] (port=60072 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g8UBO-00047p-7k for help-gnu-emacs@gnu.org; Fri, 05 Oct 2018 13:46:34 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1g8U9E-0003cB-OM for help-gnu-emacs@gnu.org; Fri, 05 Oct 2018 19:44:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 22 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:NXYDM80ZgPX3ODfurDiWh0RWxb4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 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:118130 Archived-At: Emanuel Berg 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.