From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexandre Duret-Lutz Subject: Re: #+PROPERTY: header-args:C++ will not work Date: Mon, 15 Apr 2019 16:08:55 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:50723) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hG2IK-0002T5-4I for emacs-orgmode@gnu.org; Mon, 15 Apr 2019 10:09:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hG2IH-0006lt-5l for emacs-orgmode@gnu.org; Mon, 15 Apr 2019 10:09:11 -0400 Received: from mail-qt1-x834.google.com ([2607:f8b0:4864:20::834]:43921) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hG2IG-0006kl-Dp for emacs-orgmode@gnu.org; Mon, 15 Apr 2019 10:09:08 -0400 Received: by mail-qt1-x834.google.com with SMTP id v32so19170922qtc.10 for ; Mon, 15 Apr 2019 07:09:08 -0700 (PDT) In-Reply-To: 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: emacs-orgmode@gnu.org 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+++... -- Alexandre Duret-Lutz