If my understanding is good, if I want, let's say, to use the wxWindows library,
I'll have to write (even if it's straightforward) an interop layer with C FFI.
And this is painfull, moreover when you think it can be automated, and even
more when you think it have already been done !
So the idea is to use what have already been done for other languages (Lua,
Ruby, etc...)
Yes, but there is differences between other languages and Neko.
You can surely try this way and develop a set of C macro replacing the
Lua C FFI by equivalent Neko C FFI calls, but this might not produce the
best API.
When writing such API you should think about how it can easily be used
from Neko, by using the correct Neko data strucutures. It's not very
difficult to do but might take some time depending on the size of the
API. For most API it can be done very quickly.
If you have a very very big API then maybe it might be interesting to do
so, especialy if you prefer quantity over quality, but in most of the
cases it's better to do from scratch, and this is a very good way to
master the Neko runtime representation of values.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
