lua_newthread(L)

[Rick]

Josh, are you using lua_newthread(L) in the editor or engine when calling the Lua script? I ran into an issue where coroutines are failing in Lua possibly because you are using lua_newthread(L) instead of lua_newcthread(). I guess in LuaJIT if you use lua_newcthread() it will allow coroutines to work in the situation where the Lua script is going back and forth from Lua to DLL.

 

My Question on the issue and others response

http://stackoverflow.com/questions/8459459/lua-coroutine-error-tempt-to-yield-across-metamethod-c-call-boundary/8463031#comment10471100_8463031

 

A response related to the issue

http://lua-users.org/lists/lua-l/2011-10/msg00461.html

 

 

Note that before you switched to LuaJIT I was able to get coroutines to work in Lua. Coroutines can be very valuable as it basically gives us a form of threading via Lua. I was trying to use it to split up pathfinding between game cycles when I encountered the error I describe in the stackoverflow question.

[Josh]

I don't use threading with Newton at all, so neither are called as far as I know.

[Rick]

I'll see if I can find out more information around this, but coroutines are a built-in feature of Lua and pretty powerful stuff so it would be nice if we were able to use them within LE's Lua implementation.

[Josh]

I agree, they are useful. Just make sure none of the elements in your loop change.