Lua engine setup

[tieske 0]

How does the Lua engine work? is it a single state, or a new state for every piece of code?

I noticed that this code;

Please login or register to see this code.

Keeps on printing 0 in the debug window, which leads me to believe that for every invocation of a piece of Lua code a new luaState is generated or at least a new sandbox inside a luaState.

Considering the nature of the Lua VM, this Fibaro implementation seems extremely expensive (performance wise) and is forcing duplication of code in each element of a virtual device UI. Why isn't there a sandbox/environment per device? which allows code reuse within a virtual device, easy sharing of global state, and is way faster.

[robmac 173]

it runs in individual chunks per instance of scenes so no global variables.

The virtual devices are the only exception.

[tieske 0]

what is the exception with virtual devices? Seems to me it also only runs chunks

[robmac 173]

Main loop does hold state so you can put an if around a variable and it will set once and hold value across runs. You can't access outside main loop though but some people have made use of it.

If you search we have asked may times for more open support of LUA. look at bugzilla for example

Please login or register to see this link.

There was a rumour that we may get something but just a rumour. As I say 4.x may have more