+2002-05-01 Sebastian Wilhelmi <wilhelmi@ira.uka.de>
+
+ * glib/tmpl/threads.sgml: Clarify recursion issues with
+ GMutex. (#78171)
+
2002-04-24 Matthias Clasen <maclas@gmx.de>
* gobject/gobject-sections.txt:
<note>
<para>
-#GMutex is not recursive, i.e. a thread will deadlock, if it already
-has locked @mutex while calling g_mutex_lock(). Use
-#GStaticRecMutex instead, if you need recursive mutexes.
+#GMutex is neither guaranteed to be recursive nor to be non-recursive,
+i.e. a thread could deadlock while calling g_mutex_lock(), if it
+already has locked @mutex. Use #GStaticRecMutex, if you need recursive
+mutexes.
</para>
</note>
<note>
<para>
-#GMutex is not recursive, i.e. g_mutex_trylock() will return %FALSE,
-if the current thread already has locked @mutex. Use
-#GStaticRecMutex instead, if you need recursive mutexes.
+#GMutex is neither guaranteed to be recursive nor to be non-recursive,
+i.e. the return value of g_mutex_trylock() could be both %FALSE or
+%TRUE, if the current thread already has locked @mutex. Use
+#GStaticRecMutex, if you need recursive mutexes.
</para>
</note>
<para>
#GStaticRWLock is not recursive. It might seem to be possible to
-recursivly lock for reading, but that can result in a deadlock as
+recursively lock for reading, but that can result in a deadlock as
well, due to writer preference.
</para>