laanwj on Nostr: thanks, that's a great write-up i agree a C API is the way to go for cross-language ...
thanks, that's a great write-up
i agree a C API is the way to go for cross-language compatibility, especially for dynamic loading and binding from rust, python, and other languages, as well as for automatic bindings generation, a C API is a must-have, there's a lot of precedent there
not so sure about consuming it internally, C++->C->C++ translation adds a lot of overhead and potential bugs, so might as well shortcut (but use a similar enough convention) then
i agree a C API is the way to go for cross-language compatibility, especially for dynamic loading and binding from rust, python, and other languages, as well as for automatic bindings generation, a C API is a must-have, there's a lot of precedent there
not so sure about consuming it internally, C++->C->C++ translation adds a lot of overhead and potential bugs, so might as well shortcut (but use a similar enough convention) then