Point out exceptions to the general GLib data structure locking rules.

2005-05-23  Matthias Clasen  <mclasen@redhat.com>

	* glib/tmpl/threads.sgml: Point out exceptions to the
	general GLib data structure locking rules.

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index 0c9df5f7387aae651d20ef6b04de1316a864fb8c..57dd70811e96ff9c978a5c7d5ecee200eadef8e1 100644 (file)
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,3 +1,8 @@
+2005-05-23  Matthias Clasen  <mclasen@redhat.com>
+
+       * glib/tmpl/threads.sgml: Point out exceptions to the
+       general GLib data structure locking rules.
+
 2005-05-20  Matthias Clasen  <mclasen@redhat.com>
 
        * glib/tmpl/threads.sgml: Add a paragraph about thread

diff --git a/docs/reference/glib/tmpl/threads.sgml b/docs/reference/glib/tmpl/threads.sgml
index 80f50cc95934374a27ddf4e23d545c309af5fe66..5ec8f94cd70a6a9b05f4c8dd7e6d0f548368e888 100644 (file)
--- a/docs/reference/glib/tmpl/threads.sgml
+++ b/docs/reference/glib/tmpl/threads.sgml
@@ -38,6 +38,9 @@ in a threaded GLib program. After that, GLib is completely thread safe
 (all global data is automatically locked). But individual data structure 
 instances are not automatically locked for performance reasons. So e.g. 
 you must coordinate accesses to the same #GHashTable from multiple threads.
+The two notable exceptions from this rule are #GMainLoop and #GAsyncQueue, 
+which <emphasis>are</emphasis> threadsafe and needs no further 
+application-level locking to be accessed from multiple threads.
 </para>
 
 <!-- ##### SECTION See_Also ##### -->