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)
This commit is contained in:
Matthias Clasen
2004-08-12 14:59:09 +00:00
committed by Matthias Clasen
parent 12f567e83a
commit 3fd2366a03
2 changed files with 9 additions and 4 deletions

View File

@@ -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> 2004-07-30 Matthias Clasen <mclasen@redhat.com>
* === Released 2.4.5 === * === Released 2.4.5 ===

View File

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