[glib] Fix doc build



commit 65b84bb7d0e429a30f344ebc149dc3d8d79bddda
Author: Matthias Clasen <mclasen redhat com>
Date:   Sun Oct 2 22:38:49 2011 -0400

    Fix doc build
    
    The markup here was not only broken, it was also unnecessary,
    since gtk-doc knows to apply <function></function> tags to things
    that end with () already.

 glib/gthread-posix.c |   14 ++++++--------
 1 files changed, 6 insertions(+), 8 deletions(-)
---
diff --git a/glib/gthread-posix.c b/glib/gthread-posix.c
index c47fc0d..51b886d 100644
--- a/glib/gthread-posix.c
+++ b/glib/gthread-posix.c
@@ -866,17 +866,15 @@ g_cond_timedwait (GCond  *cond,
  * GPrivate:
  *
  * The #GPrivate struct is an opaque data structure to represent a
- * thread-local data key.  It is approximately equivalent to the
- * <function>pthread_setspecific()</function>/<function>pthread_getspecific()</function>
- * APIs on POSIX and to
- * <function>TlsSetValue()</function>/<function>TlsGetValue<()/function> on
- * Windows.
+ * thread-local data key. It is approximately equivalent to the
+ * pthread_setspecific()/pthread_getspecific() APIs on POSIX and to
+ * TlsSetValue()/TlsGetValue() on Windows.
  *
- * If you don't already know why you might want this functionality, then
- * you probably don't need it.
+ * If you don't already know why you might want this functionality,
+ * then you probably don't need it.
  *
  * #GPrivate is a very limited resource (as far as 128 per program,
- * shared between all libraries).  It is also not possible to destroy a
+ * shared between all libraries). It is also not possible to destroy a
  * #GPrivate after it has been used. As such, it is only ever acceptable
  * to use #GPrivate in static scope, and even then sparingly so.
  *



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]