AutomaticComponentToolkit
AutomaticComponentToolkit copied to clipboard
Autodesk
A toolkit to automatically generate software components: abstract API, implementation stubs and language bindings
``` ``` `class=ClassIsNotDefined` is not detected by the code generator.
We are using cdynamic.cc headers at the moment for the cgo bindings. Is there a way to statically link the libraries with go?
Currently callbacks are making the cgo headers not compile.
Pointer variables are making the headers not compile. We tried to use interface{} style-pointers in order to abstract this for the user, but they seemed to crash. My suggestion would...
We would need to call unload library with the wrapper destructor, but I am a bit helpless how this works. @qmuntal: Is there a chance you can take a look...
Currently, component injection on the implementation side introduces static global variables - which are not a good idea in my opinion to introduce. My suggestion would be, that we refactor...
Currently headers are not multi-thread-safe, and the calling application needs to take care on having the right multithread-behaviour. A simple optional (?) option would be to introduce a header-mutex with...
Currently, the error string propagation works by calling `RegisterErrorMessage` on the base class whenever an exception is caught on the component side, which is then propagated to the binding and...
Currently function callbacks are passed directly over the interface as arguments. This leads to 2 issues: 1. We cannot journal calls into these callbacks from within the implementation - which...
but also do not trigger a generation error. In my opinion, nothing speaks against allowing and implementing this feature. Probably this is related to issue #104