On Fre 04.05.2007 12:26, Nicolas Cannasse wrote:
>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.) ???
In case of out-of-memory, the GC display an error message and then the
VM exits. In case of segfault, the app crashes on windows but for some
signals on Linux (Bus Error) a Neko exception is thrown. This makes
things more easy for debugging.
Which is similar like lua, isn't it?!
Thanks for answers ;-)
BR
Aleks
--
Neko : One VM to run them all
(http://nekovm.org)
