From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: #+PROPERTY: header-args:C++ will not work Date: Tue, 23 Apr 2019 10:28:01 +0200 Message-ID: <871s1tw2ge.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:42607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hIqmi-0001X5-GY for emacs-orgmode@gnu.org; Tue, 23 Apr 2019 04:28:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hIqmg-0007qc-Fq for emacs-orgmode@gnu.org; Tue, 23 Apr 2019 04:28:12 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:49495) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hIqmc-0007o8-TB for emacs-orgmode@gnu.org; Tue, 23 Apr 2019 04:28:08 -0400 In-Reply-To: (Alexandre Duret-Lutz's message of "Mon, 15 Apr 2019 16:08:55 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Alexandre Duret-Lutz Cc: emacs-orgmode@gnu.org Hello, Alexandre Duret-Lutz writes: > On Mon, Apr 15, 2019 at 2:53 PM Alexandre Duret-Lutz wrote: >> Unfortunately, this does not work for C++ blocks. > > I just noticed that I could change all my C++ blocks into cpp blocks and > then use header-args:cpp without any problem. The org-mode manual > states that the identifier for the C++ language is "C++" > (https://orgmode.org/manual/Languages.html) but the same page links to > some babel documentation > (https://orgmode.org/worg/org-contrib/babel/languages.html) > where it is listed as "cpp". > > ORG-NEWS has one example using C++, but the test suite only has cpp examples. > > There is some hint on > https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-C.html#orgea7b004 > that using cpp might not fully work (?). And clearly while lisp/org-src.el has > many functions implemented for both cpp and C++, its not always complete. > For instance it defines org-babel-header-args:C++ > but there is no org-babel-header-args:cpp, meaning incomplete completion for > cpp blocks header-args. > > From all that it feels like the documentation wants us to use C++, and that > the code is trying to keep cpp for backward compatibility (?), but that each > option has different drawbacks. > > I'll stick to C++ and header-args:C+++... I think we should use enforce using cpp everywhere instead of C++, since it is more consistent. Patches welcome, of course :) Regards, -- Nicolas Goaziou