Yeah, that works great for a lot of tasks, it's just if you need any of the scripts to modify engine-wide global variables it falls down, but then you've got extra issues of making sure there's no access errors... maybe it'd just be easier to constrain myself and future users!
I think during my investigations there was some way of getting Lua to essentially "copy" a state into a new one so that you'd have access to the parent state's globals.
There's also the issue of blocking functions, for which wrapping lua_yield and lua_resume might be handy - although I could never get my head around those two functions!
I don't want to sound like I'm not grateful - I am, immensely - I'm just pointing out some further extensions if you so wished to do it. No doubt that if you don't others and myself will kludge our own solutions together ^^.
Cheers,
Ed
I think during my investigations there was some way of getting Lua to essentially "copy" a state into a new one so that you'd have access to the parent state's globals.
There's also the issue of blocking functions, for which wrapping lua_yield and lua_resume might be handy - although I could never get my head around those two functions!
I don't want to sound like I'm not grateful - I am, immensely - I'm just pointing out some further extensions if you so wished to do it. No doubt that if you don't others and myself will kludge our own solutions together ^^.
Cheers,
Ed