Hello, Alexandre Duret-Lutz <a...@lrde.epita.fr> writes:
> On Mon, Apr 15, 2019 at 2:53 PM Alexandre Duret-Lutz <a...@lrde.epita.fr> > 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
