RE: [mlist] RE: [GD-General] Off the shelf scripting languages

[Ivan-Assen I. <as...@ha...>]

> The latest version of Lua (5.0) is mostly "stackless", so 
> latent functions are supported, and so you don't have 
> troubles with interpreter state embedded in the C stack (if 
> that's the problem you're referring to).  You would still 
> have to write some code to serialize the VM and heap state.

There are two separate problems.

To support latent functions, the interpreter must be able to yield
(as in "yield vs. return" when you talk about coroutines)
control back to the thread scheduler that runs it when it encounters
a latent function call - this is more convoluted than the usual
"run this script for it's side effects and return a value when it's
done"
model of embedding.

To support serialization, the interpreter stacks must not only
NOT be intertwined with the C stack - the "stackless" property of
Stackless Python, and, I presume Lua 5.0 - but also must not contain
any live pointers to real memory - or provide a mechanism for
serializing the state of each execution thread.

regards,
Assen