From d38febf6b3e483fc27ca90192c00f8688ca4fb7a Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Mon, 23 May 2005 19:10:54 +0000 Subject: [PATCH] Point out exceptions to the general GLib data structure locking rules. 2005-05-23 Matthias Clasen * glib/tmpl/threads.sgml: Point out exceptions to the general GLib data structure locking rules. --- docs/reference/ChangeLog | 5 +++++ docs/reference/glib/tmpl/threads.sgml | 3 +++ 2 files changed, 8 insertions(+) diff --git a/docs/reference/ChangeLog b/docs/reference/ChangeLog index 0c9df5f..57dd708 100644 --- a/docs/reference/ChangeLog +++ b/docs/reference/ChangeLog @@ -1,3 +1,8 @@ +2005-05-23 Matthias Clasen + + * glib/tmpl/threads.sgml: Point out exceptions to the + general GLib data structure locking rules. + 2005-05-20 Matthias Clasen * glib/tmpl/threads.sgml: Add a paragraph about thread diff --git a/docs/reference/glib/tmpl/threads.sgml b/docs/reference/glib/tmpl/threads.sgml index 80f50cc..5ec8f94 100644 --- a/docs/reference/glib/tmpl/threads.sgml +++ b/docs/reference/glib/tmpl/threads.sgml @@ -38,6 +38,9 @@ in a threaded GLib program. After that, GLib is completely thread safe (all global data is automatically locked). But individual data structure instances are not automatically locked for performance reasons. So e.g. you must coordinate accesses to the same #GHashTable from multiple threads. +The two notable exceptions from this rule are #GMainLoop and #GAsyncQueue, +which are threadsafe and needs no further +application-level locking to be accessed from multiple threads. -- 2.7.4