- Method shared_lock
This function attempts to lock the mutex. If the mutex is already locked by a different thread the current thread will sleep until the mutex is unlocked. The value returned is the 'key' to the lock. When the key is destructed or has no more references the mutex will automatically be unlocked.
typeargument specifies what lock() should do if the mutex is already locked exclusively by this thread:
Throw an error.
Sleep until the mutex is unlocked. Useful if some other thread will unlock it.
Return zero. This allows recursion within a locked region of code, but in conjunction with other locks it easily leads to unspecified locking order and therefore a risk for deadlocks.
Seconds to wait before the timeout is reached.
Nano (1/1000000000) seconds to wait before the timeout is reached. This value is added to the number of seconds specified by
A timeout of zero seconds disables the timeout.
Note that the timeout is approximate (best effort), and may be exceeded if eg the interpreter is busy after the timeout.
Note that if the current thread already holds a shared key, a new will be created without waiting, and regardless of the value of
If the mutex is destructed while it's locked or while threads are waiting on it, it will continue to exist internally until the last thread has stopped waiting and the last MutexKey has disappeared, but further calls to the functions in this class will fail as is usual for destructed objects.
Support for shared keys was added in Pike 8.1.
- See also