Open dbenoit17 opened 5 years ago
If dynamic-ffi can self-host like this, we can also generate bindings for other high level languages like python!
I am using this for RacketCS and seems to work until now (testing trivial examples). What should I expect to break?
Hi Paulo,
I have not tested the library with RacketCS yet, but I was under the impression that it would not work at all. The dynamic FFI is currently written using Racket's C API, which I thought would be unsupported in RacketCS.
I think we could rewrite that file easily in Racket using the builtin FFI lib, and we could probably even use the dynamic ffi to generate such bindings.
Do you know if there is some compatibility layer in the works between RacketCS and the C API? That would make it unnecessary to rewrite the file.
I think this could be somewhat trivially accomplished by using dynamic-ffi to generate static bindings to itself.