emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] #+PROPERTY: header-args:C++ will not work


From: Nicolas Goaziou
Subject: Re: [O] #+PROPERTY: header-args:C++ will not work
Date: Tue, 23 Apr 2019 10:28:01 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)

Hello,

Alexandre Duret-Lutz <address@hidden> writes:

> On Mon, Apr 15, 2019 at 2:53 PM Alexandre Duret-Lutz <address@hidden> 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]