Re:Neverflow: Set of C macros that guard against buffer over...
by pjmlp on Friday June 02, 2023 @11:36AM
(#36166574)
Unless we are talking about an obscure platform or some PIC CPU, a C++ compiler is available on the same box as the C compiler.
Second, extern "C" exists.
Third, in what concerns clang and MSVC, the C library is actually implemented in C++ with extern "C".
Re:Neverflow: Set of C macros that guard against buffer over...
by epistasis on Friday June 02, 2023 @12:22PM
(#36167161)
My single sentence may have been too concise, there are two concepts here: 1) the tool chain may or may not exist, and 2) bringing in that tool chain to the build system.
Even if it's the "same" toolchain for compiling C++ as it is C, adding the complexity of an additional language to the build process, and the extra versioning headaches that C++ adds over C, is enough to kill library adoption.
As I said originally, providing bindings is not the challenge, it's all the other stuff.
Re:Neverflow: Set of C macros that guard against buffer over...
by pjmlp on Friday June 02, 2023 @02:39PM
(#36169048)
"To Save C, We Must Save ABI"
https://thephd.dev/to-save-c-we-must-save-abi-fixing-c-funct...
https://overcast.fm/+LfVPHmBTo
Even if the tool chain exists, it must be adopted, unless you can rely on binaries being available for your end users, which will never be the case for a library which is just starting our. And adding another dependency to your build process, especially one as complex and with as many breaking version changes as C++, is a lot of work to take on.