[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Lua State Thread Safety
- From: Paige DePol <lual@...>
- Date: Sun, 13 Jul 2014 19:52:41 -0500
On Jul 13, 2014, at 7:36 PM, Austin Einter <firstname.lastname@example.org> wrote:
> Hi All
> Suppose I have Lua State L as a global variable in my C program.
> If it is accessed and used by two different threads, is it required for me to protect the Lua State by using a semaphore/mutex.
> Lua State internally has a semaphore/mutex to protect itself.
> Please let me know.
I believe you need to #define the `lua_lock` and `lua_unlock` macros to perform whichever locking mechanism you desire for Lua thread safety, these macros are not defined to do anything by default.
Searching the archives for `lua_lock` brings up a number of previous discussions, some of which are on the use of `lua_lock` and `lua_unlock` in threaded environments.