Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

Commit

Permalink
Document the necessity to call g_thread_init() when using threads (even
Browse files Browse the repository at this point in the history
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)
  • Loading branch information
Matthias Clasen authored and Matthias Clasen committed Aug 12, 2004
1 parent 305e8c8 commit 31e039c
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 4 deletions.
7 changes: 7 additions & 0 deletions docs/reference/ChangeLog
Original file line number Diff line number Diff line change
@@ -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.
Expand Down
7 changes: 3 additions & 4 deletions docs/reference/glib/tmpl/threads.sgml
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down

0 comments on commit 31e039c

Please sign in to comment.