luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-04-28 01:56:52 +02:00
Code Issues Packages Projects Releases Wiki Activity

gthread: remove a stray reference to GStaticMutex

Browse Source
This commit is contained in:
Dan Winship 2011-09-29 09:58:57 -04:00
parent 76d2f7fa6a
commit f992c240e8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
glib/gthread.c
View File

@ -132,13 +132,13 @@
* G_LOCK_DEFINE: * G_LOCK_DEFINE:
* @name: the name of the lock. * @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 * with the advantage that they will expand to nothing in programs
* compiled against a thread-disabled GLib, saving code and memory * compiled against a thread-disabled GLib, saving code and memory
* there. #G_LOCK_DEFINE defines a lock. It can appear anywhere * there. #G_LOCK_DEFINE defines a lock. It can appear anywhere
* variable definitions may appear in programs, i.e. in the first block * variable definitions may appear in programs, i.e. in the first block
* of a function or outside of functions. The @name parameter will be * 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 * 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 * of the variable you intent to protect with the lock. Look at our
* <function>give_me_next_number()</function> example using the * <function>give_me_next_number()</function> example using the