C bindings clarification

[Hex4dec]

While the C bindings mentioned in the README could theoretically be used from C, it is incredibly painful to and almost impossible. It should be clarified that they should only be used for C-style programming on a C++ compiler. (I have used all available bindings and have come to this conclusion)

(if the creators of literally any Jolt C bindings are reading this, go take inspiration from how the ODE physics engine does it)

[NEO97online]

What problem did you have?

I'm using https://github.com/amerkoleci/joltc in Jai (not even in C or C++ at all) and its working great. What is impossible about it?

[Hex4dec]

They are impossible to package since they require networking at build time (and their maintainers reject pull requests that use submodules instead), the library you listed has very aggressive namespacing, they are annoyingly strict with memory allocation and is often difficult to debug, Jolt uses a lot of structures and classes so it is annoying to always MakeThat() and CreateThis(), the bindings often have little to no documentation, and ironically the sample (thats right, sample, not samples) of the library you listed is in C++ and even uses C++ features. These libraries are not meant for consumption from C.

[jrouwe]

Moving to a discussion as I'm not involved in the C bindings so there's nothing I can 'fix' here. I'm also curious what's wrong with the C bindings that exist.