Re: GDNative thick binding design

[Michael Hardeman <mhardeman25@gmail.com>]

On Wednesday, October 21, 2020 at 12:17:00 PM UTC-4, persan....@gmail.com wrote:
> Michael 
> The "clone" is just an instantiation of the Binding template in the from 
> the same github-project. The important thing is the total structure that 
> is forcing hiding of the generated C-binding and it also makes it 
> trivial to regenerate the low-level stuff when the header-files changes 
> whats in the pipe as well is to semiautomatic generate the exported 
> interfaces and implementations, but the initial attempts are to crude to 
> put in the public they are just hacks so far. 
> 
> I am happy to to contribute but since the original project in my opinion 
> needed to much rework to start a discussion. I just instantiated my 
> template for C-bindings, and completed the .c and .sed files. 
> 
> And please see my project as an input with ideas on how I do believe 
> bindings to larger C/C++ libraries shall be done and not as a new clone 
> since i don't intend to do anything more with it that provide a 
> structure for a binding project. 
> 
> /Regards 
> /P
> On 21/10/2020 05:34, Michael Hardeman wrote: 
> > why create a clone of my project idea with generated bindings instead of just contributing to the working one I've already made? 
> >

I initially generated bindings to the headers, but they ended up needing significant work to be usable. I don't think automated generation of the binding is practical.
Since your program ends up being a dynamic library with 3 functions, and 1 of them is passed a pointer to the whole godot api as a single struct I don't think having multiple files is actually useful. It's a tricky API to use, and to bind to.