Say that ref/unref are thread-safe now. (#322883, Christophe Fergeau)

2006-04-18  Matthias Clasen  <mclasen@redhat.com>

	* gobject/tut_gobject.xml: Say that ref/unref are thread-safe now.
	(#322883, Christophe Fergeau)
This commit is contained in:
Matthias Clasen 2006-04-18 18:36:44 +00:00 committed by Matthias Clasen
parent ab3dd5e413
commit 442ef9d902
2 changed files with 6 additions and 1 deletions

View File

@ -1,3 +1,8 @@
2006-04-18 Matthias Clasen <mclasen@redhat.com>
* gobject/tut_gobject.xml: Say that ref/unref are thread-safe now.
(#322883, Christophe Fergeau)
2006-04-05 Matthias Clasen <mclasen@redhat.com>
* gobject/tmpl/signals.sgml: Document class_offset 0.

View File

@ -323,7 +323,7 @@ void g_object_run_dispose (GObject *object);
<para>
The functions <function><link linkend="g-object-ref">g_object_ref</link></function>/<function><link linkend="g-object-unref">g_object_unref</link></function> respectively
increase and decrease the reference count. None of these function is thread-safe.
increase and decrease the reference count.These functions are thread-safe as of GLib 2.8.
The reference count is, unsurprisingly, initialized to one by
<function><link linkend="g-object-new">g_object_new</link></function> which means that the caller
is currenly the sole owner of the newly-created reference.