2017-09-13 04:42:36 +08:00
<?xml version="1.0" encoding="UTF-8" ?>
2021-06-05 00:03:15 +08:00
<class name= "Mutex" inherits= "RefCounted" version= "4.0" >
2017-09-13 04:42:36 +08:00
<brief_description >
2019-06-22 07:04:47 +08:00
A synchronization mutex (mutual exclusion).
2017-09-13 04:42:36 +08:00
</brief_description>
<description >
2019-06-22 07:04:47 +08:00
A synchronization mutex (mutual exclusion). This is used to synchronize multiple [Thread]s, and is equivalent to a binary [Semaphore]. It guarantees that only one thread can ever acquire the lock at a time. A mutex can be used to protect a critical section; however, be careful to avoid deadlocks.
2017-09-13 04:42:36 +08:00
</description>
<tutorials >
2021-11-15 17:43:07 +08:00
<link title= "Using multiple threads" > $DOCS_URL/tutorials/performance/using_multiple_threads.html</link>
2017-09-13 04:42:36 +08:00
</tutorials>
<methods >
<method name= "lock" >
2021-07-30 21:28:05 +08:00
<return type= "void" />
2017-09-13 04:42:36 +08:00
<description >
2019-06-22 07:04:47 +08:00
Locks this [Mutex], blocks until it is unlocked by the current owner.
2021-03-04 01:27:09 +08:00
[b]Note:[/b] This function returns without blocking if the thread already has ownership of the mutex.
2017-09-13 04:42:36 +08:00
</description>
</method>
<method name= "try_lock" >
2021-07-30 21:28:05 +08:00
<return type= "int" enum= "Error" />
2017-09-13 04:42:36 +08:00
<description >
2019-06-22 07:04:47 +08:00
Tries locking this [Mutex], but does not block. Returns [constant OK] on success, [constant ERR_BUSY] otherwise.
2021-03-04 01:27:09 +08:00
[b]Note:[/b] This function returns [constant OK] if the thread already has ownership of the mutex.
2017-09-13 04:42:36 +08:00
</description>
</method>
<method name= "unlock" >
2021-07-30 21:28:05 +08:00
<return type= "void" />
2017-09-13 04:42:36 +08:00
<description >
2019-06-22 07:04:47 +08:00
Unlocks this [Mutex], leaving it to other threads.
2021-03-04 01:27:09 +08:00
[b]Note:[/b] If a thread called [method lock] or [method try_lock] multiple times while already having ownership of the mutex, it must also call [method unlock] the same number of times in order to unlock it correctly.
2017-09-13 04:42:36 +08:00
</description>
</method>
</methods>
</class>