by wheresvic4 on 1/16/22, 8:02 AM with 12 comments
by coldtea on 1/16/22, 7:15 PM
What prevents GCC and Clang (and co from Intel/MS) saving a sidecar file next to a program/.so with all the functions and their argument types, struct structures, etc. in some agreed upon format for easy parsing / use? Could even be emitted based on some annotation/pragma like #export before the function declaration.
Is it just that nobody really cares to coordinate such a solution?
by pjmlp on 1/16/22, 8:20 AM
"Making Libraries Consumable for Non-C++ Developers"
by wolframhempel on 1/16/22, 1:09 PM
Our argument for this weird symbiosis was that we wanted the popularity of the NodeJS ecosystem at the time with the performance of C++ - and we achieved this to an at least satisfactory degree.
When it came to building binaries based on the mixed codebases, especially for windows, things were a lot more challenging.
by henrydark on 1/16/22, 1:28 PM
To tie it back to the piece, it would be pretty easy to generate code that outputs function definitions from an apache arrow scheme in both C and a target interpreted language such as python (e.g. ctypes bindings).
by sharikous on 1/16/22, 11:39 AM