Document the necessity to call g_thread_init() when using threads (even

2004-08-12  Matthias Clasen  <mclasen@redhat.com>

	* glib/tmpl/threads.sgml: Document the necessity to call
	g_thread_init() when using threads
	(even non-gthreads).  (#149490, Vincent Untz)

diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
index 38d8ec2..bcd21e1 100644 (file)
--- a/docs/reference/ChangeLog
+++ b/docs/reference/ChangeLog
@@ -1,3 +1,10 @@
+2004-08-12  Matthias Clasen  <mclasen@redhat.com>
+
+       * glib/tmpl/threads.sgml: Document the necessity to call
+       g_thread_init() when using threads 
+       (even non-gthreads).  (#149490, Vincent Untz)
+
+
 Tue Aug  3 16:43:22 2004  Matthias Clasen  <maclas@gmx.de>
 
        * glib/glib-sections.txt: Add a section for GOption.

diff --git a/docs/reference/glib/tmpl/threads.sgml b/docs/reference/glib/tmpl/threads.sgml
index c1bc4f3..72104c4 100644 (file)
--- a/docs/reference/glib/tmpl/threads.sgml
+++ b/docs/reference/glib/tmpl/threads.sgml
@@ -142,10 +142,9 @@ This struct should only be used, if you know, what you are doing.
 <!-- ##### FUNCTION g_thread_init ##### -->
 
 <para>
-Before you use a thread related function in GLib, you should
-initialize the thread system. This is done by calling
-g_thread_init(). Most of the time you will only have to call
-<literal>g_thread_init(NULL)</literal>. 
+If you use GLib from more than one thread, you must initialize
+the thread system by calling g_thread_init(). Most of the time you 
+will only have to call <literal>g_thread_init (NULL)</literal>. 
 </para>
 
 <note>