Re: void* in Lua_State for Application?

[Roberto Ierusalimschy <roberto@...>]

> Actually there was a good reason for which luai_userstateclose could not be used to free the private object associated to the main Lua thread.
> 
> [...]
> [...]
>   
> So the bottom line for this is the need for fine-grain synchronization between the lua-State ant the associated private data, i.e. that no Lua or native code call should be done in a lua_state after the corresponding luai_userstatefree or luai_userstateclose has been called.
> 
> What is your opinion about this?

I guess you are right. In fact, the current place of luai_userstateclose
might be considered a bug.

-- Roberto