[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Yielding across lua_load
- From: "Soni L." <fakedme@...>
- Date: Sun, 11 Oct 2015 18:20:47 -0300
On 11/10/15 04:09 PM, Tim Hill wrote:
On Oct 10, 2015, at 8:07 PM, Soni L. <firstname.lastname@example.org> wrote:
On 10/10/15 11:51 PM, Tim Hill wrote:
On Oct 10, 2015, at 6:57 AM, Christian N. <email@example.com <mailto:firstname.lastname@example.org>> wrote:
On 2015-10-08 19:48 +0200, Soni L. wrote:
I don't think that would be possible, as yielding would jump outside lua_load using longjmp, losing any information lua_load has stored on the C stack (probably even leaking memory). However, using something like the C++ library Boost.Context or Boost.Coroutine, a workaround might maybe be possible as these libraries provide a way to sort of save the C stack.
More to the point is why the original OP feels yielding during lua_load() is necessary.
You can't yield during string.gsub callback either, but that's not relevant.
I actually do have an use for yielding during lua_load() and it has to do with a Minecraft mod called OpenComputers. I can't remember what it was because it happened a while ago but it did stop me from finishing what I was doing.
It's also useful for JIT-tracing to Lua. (easier to reset/use as you don't have to worry about state as much) Especially so when combined with a 3rd party cooperative multitasking library. (you wouldn't be able to keep the other threads going unless you yielded, which would kill the load() and possibly the whole thread as well, because it would error)
If you are worried about compiler overhead, why not spin up a dedicated Lua state on its own thread and use that as an async compile engine? You can shuttle the result back as bytecode and then feed this to lua_load() for very fast load times.
When did I say anything about compiler overhead?
Disclaimer: these emails may be made public at any given time, with or without reason. If you don't agree with this, DO NOT REPLY.