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)
dieterv · Aug 12, 2004 · 3fd2366 · 3fd2366
1 parent 12f567e
commit 3fd2366
Show file tree

Hide file tree

Showing 2 changed files with 9 additions and 4 deletions.
diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog
@@ -1,3 +1,9 @@
+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)
+
 2004-07-30  Matthias Clasen  <mclasen@redhat.com>
 
 	* === Released 2.4.5 ===

diff --git 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>