[glib] gthread-posix: Remove misleading documentation comments
- From: Jasper St. Pierre <jstpierre src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib] gthread-posix: Remove misleading documentation comments
- Date: Fri, 6 Jan 2012 19:41:19 +0000 (UTC)
commit d141940bc67a1c101dbd893e0b5247d931515159
Author: Jasper St. Pierre <jstpierre mecheye net>
Date: Fri Jan 6 14:29:45 2012 -0500
gthread-posix: Remove misleading documentation comments
g_thread_init() has done nothing since 2.32, so while the function
still can be used if "g_thread_init() has not yet been called",
it won't do nothing in that case, it will just perform normally.
glib/gthread-posix.c | 15 ---------------
1 files changed, 0 insertions(+), 15 deletions(-)
---
diff --git a/glib/gthread-posix.c b/glib/gthread-posix.c
index 79f5034..faa6004 100644
--- a/glib/gthread-posix.c
+++ b/glib/gthread-posix.c
@@ -195,9 +195,6 @@ g_mutex_clear (GMutex *mutex)
* current thread will block until @mutex is unlocked by the other
* thread.
*
- * This function can be used even if g_thread_init() has not yet been
- * called, and, in that case, will do nothing.
- *
* <note>#GMutex is neither guaranteed to be recursive nor to be
* non-recursive. As such, calling g_mutex_lock() on a #GMutex that has
* already been locked by the same thread results in undefined behaviour
@@ -221,9 +218,6 @@ g_mutex_lock (GMutex *mutex)
*
* Calling g_mutex_unlock() on a mutex that is not locked by the
* current thread leads to undefined behaviour.
- *
- * This function can be used even if g_thread_init() has not yet been
- * called, and, in that case, will do nothing.
*/
void
g_mutex_unlock (GMutex *mutex)
@@ -242,9 +236,6 @@ g_mutex_unlock (GMutex *mutex)
* it immediately returns %FALSE. Otherwise it locks @mutex and returns
* %TRUE.
*
- * This function can be used even if g_thread_init() has not yet been
- * called, and, in that case, will immediately return %TRUE.
- *
* <note>#GMutex is neither guaranteed to be recursive nor to be
* non-recursive. As such, calling g_mutex_lock() on a #GMutex that has
* already been locked by the same thread results in undefined behaviour
@@ -764,9 +755,6 @@ g_cond_wait (GCond *cond,
* If no threads are waiting for @cond, this function has no effect.
* It is good practice to hold the same lock as the waiting thread
* while calling this function, though not required.
- *
- * This function can be used even if g_thread_init() has not yet been
- * called, and, in that case, will do nothing.
*/
void
g_cond_signal (GCond *cond)
@@ -785,9 +773,6 @@ g_cond_signal (GCond *cond)
* If no threads are waiting for @cond, this function has no effect.
* It is good practice to lock the same mutex as the waiting threads
* while calling this function, though not required.
- *
- * This function can be used even if g_thread_init() has not yet been
- * called, and, in that case, will do nothing.
*/
void
g_cond_broadcast (GCond *cond)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]