From: Matthias Clasen <matthiasc@src.gnome.org>
Date: Tue, 29 Jul 2003 22:37:37 +0000 (+0000)
Subject: Add paragraph about multi-threading policy.
X-Git-Url: http://git.openbox.org/?a=commitdiff_plain;h=e7fde02e4fd3fad8053a9f2f8f4a3dc4c4730842;p=dana%2Fcg-glib.git

Add paragraph about multi-threading policy.

	* glib/glib-docs.sgml: Add paragraph about multi-threading policy.
---

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index 20070663..d75ffe17 100644
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,5 +1,7 @@
 2003-07-30  Matthias Clasen  <maclas@gmx.de>
 
+	* glib/glib-docs.sgml: Add paragraph about multi-threading policy.
+
 	* glib/glib-sections.txt: Rename g_read_link to g_file_read_link.
 
 2003-07-29  Matthias Clasen  <maclas@gmx.de>
diff --git a/docs/reference/glib/glib-docs.sgml b/docs/reference/glib/glib-docs.sgml
index 2be3fa5c..9459933a 100644
--- a/docs/reference/glib/glib-docs.sgml
+++ b/docs/reference/glib/glib-docs.sgml
@@ -80,6 +80,12 @@ loop abstraction, and so on. It works on many UNIX-like platforms, Windows,
 OS/2 and BeOS. GLib is released under the GNU Library General Public License 
 (GNU LGPL). 
     </para>
+    <para>
+The general policy of GLib is that all functions are invisibly threadsafe with the 
+exception of data structure manipulation functions, where, if you have two threads
+manipulating the <emphasis>same</emphasis> data structure, they must use a lock to
+synchronize their operation.
+    </para>
 
     &glib-Building;
     &glib-Cross;