You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new project was just announced [https://groups.google.com/forum/#!msg/golang-nuts/3I7TzmEirbo/x07zmVNcAgAJ] https://cgogen.com/ which generates cgo bindings automatically by parsing the underlying C source code. Sounds familiar?
I took a quick look and there is definitely a lot we could reuse, especially the conversion from C to Go structs. However, I do not think that the bindings should look like the result of cgogen:
A new project was just announced [https://groups.google.com/forum/#!msg/golang-nuts/3I7TzmEirbo/x07zmVNcAgAJ] https://cgogen.com/ which generates cgo bindings automatically by parsing the underlying C source code. Sounds familiar?
The design decisions of cgogen are documented here https://github.com/xlab/cgogen/wiki/Design-decisions
I took a quick look and there is definitely a lot we could reuse, especially the conversion from C to Go structs. However, I do not think that the bindings should look like the result of cgogen:
Should we take a deeper look?
The text was updated successfully, but these errors were encountered: