[glib] gthread: remove a stray reference to GStaticMutex
- From: Dan Winship <danw src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib] gthread: remove a stray reference to GStaticMutex
- Date: Thu, 29 Sep 2011 13:59:18 +0000 (UTC)
commit f992c240e86986dbede0124d1038e0223d8491dd
Author: Dan Winship <danw gnome org>
Date: Thu Sep 29 09:58:57 2011 -0400
gthread: remove a stray reference to GStaticMutex
glib/gthread.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/glib/gthread.c b/glib/gthread.c
index 83aef42..45b5850 100644
--- a/glib/gthread.c
+++ b/glib/gthread.c
@@ -132,13 +132,13 @@
* G_LOCK_DEFINE:
* @name: the name of the lock.
*
- * The %G_LOCK_* macros provide a convenient interface to #GStaticMutex
+ * The %G_LOCK_* macros provide a convenient interface to #GMutex
* with the advantage that they will expand to nothing in programs
* compiled against a thread-disabled GLib, saving code and memory
* there. #G_LOCK_DEFINE defines a lock. It can appear anywhere
* variable definitions may appear in programs, i.e. in the first block
* of a function or outside of functions. The @name parameter will be
- * mangled to get the name of the #GStaticMutex. This means that you
+ * mangled to get the name of the #GMutex. This means that you
* can use names of existing variables as the parameter - e.g. the name
* of the variable you intent to protect with the lock. Look at our
* <function>give_me_next_number()</function> example using the
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]