Repository navigation
[SUGGESTION] cppfront transpiler parameter to generate interoperability with C #612
Description
Activity
The generation should be restricted to:
Sounds like a prime use-case for metafunctions.
E.g.,algo: @c_api (r: std::span<int>) = { … }could generate the usual Cpp2 declaration, and a Cpp1
extern "C"at lower time that looks like:extern "C" { void algo(int* rp, std::size_t rs) { algo(std::span<int>{rp, rs}); } }
Reacted by Raf (Raffaele Rialdi)- Repository owner locked and limited conversation to collaborators
on Aug 30, 2023
My suggestion does not touch
cppfrontat all, but is a transpiler parameter to automatically generateextern Cfunctions to overcome the binary compatibility issues in C++.The goal is to allow consuming C++ pure libraries from other languages without messing with the mangled names and risking breaking changes with future versions of the C++ libraries and/or compilers.
The generation should be restricted to:
If I understood correctly,
cppfrontmakes the parameter direction clear usinginandout. This metadata can be used to apply the patterns to correctly allocate/deallocate the memory for the parameters.It could be also useful to define a "type transformer" that can be used by the transpiler to extend the types that can be used in the generation. For example, a
std::vector<T>could be mapped toT*and length.