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 0c9df5f..57dd708 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 80f50cc..5ec8f94 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 ##### -->