Hi, on another list there was some questions which I can't answer by my self about neko:
---
>1) It must always test results of its internal operations, such as > malloc, and return error. lua simply exit()s when memory is over. http://www.nekovm.org/doc/ffi#managing_memory
There's no mention how neko tests results in its internals. --- I think this will be handled by GC but what happens?! 1.) Exceptions 2.) Segfault, I don't think so ;-) 3.) ??? ---
>3) It should support non-blocking oprations, such as > > v = get_variable(...) > if (v == NOT_READY) ...
--- I think this could be done with threads but I'am not sure. The point here is: There is a server which handles http-requests and should not be blocked during neko works on his task. Maybe I have overread something or missunderstand, please point me to the right way ;-). BR Aleks -- Neko : One VM to run them all (http://nekovm.org)
