btw, I'm wondering about Neko interop. I think what slow the Neko adoption is
the lack of library (and IDE / Debugger too).
Neko syntax is pretty near from C one so IDE support should be quite
easy to do. A debugger would be nice, but it require some work since
maybe you want to debug the language targeting Neko and not Neko itself.
> Do you think it would be hard to
implement an interop layer for... let's say, Lua ou Ruby or Python libs ? that
way Neko could use the work already done, and, avoid new coders to learn
entirely new API. Or maybe a SWIG layer could be interesting too.
I think you mean the C FFI ?
Neko FFI is very easy to learn and use, since it completely abstracts
the VM. In other languages (I think same in Lua, Ruby and Python) you're
directly manipulating the VM stack which is not the case in Neko. It
make it complicated to reuse directly other language libraries, although
I think it's possible to port them quite easily.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
