[glib] Cosmetics
- From: Matthias Clasen <matthiasc src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib] Cosmetics
- Date: Mon, 3 Oct 2011 03:54:31 +0000 (UTC)
commit 9d989c7b8aebda0e56aaadb843def0f48f909156
Author: Matthias Clasen <mclasen redhat com>
Date: Sun Oct 2 23:53:56 2011 -0400
Cosmetics
glib/gthread.c | 9 +++++----
1 files changed, 5 insertions(+), 4 deletions(-)
---
diff --git a/glib/gthread.c b/glib/gthread.c
index 1c6282f..75ccb3e 100644
--- a/glib/gthread.c
+++ b/glib/gthread.c
@@ -88,7 +88,7 @@
* Finally there are primitives to create and manage threads (#GThread).
*
* The threading system is initialized with g_thread_init().
- * You may call any other glib functions in the main thread before
+ * You may call any other GLib functions in the main thread before
* g_thread_init() as long as g_thread_init() is not called from
* a GLib callback, or with any locks held. However, many libraries
* above GLib do not support late initialization of threads, so
@@ -97,7 +97,7 @@
* Please note that since version 2.24 the GObject initialization
* function g_type_init() initializes threads. Since 2.32, creating
* a mainloop will do so too. As a consequence, most applications,
- * including those using GTK+ will run with threads enabled.
+ * including those using GTK+, will run with threads enabled.
*
* After calling g_thread_init(), GLib is completely thread safe
* (all global data is automatically locked), but individual data
@@ -582,7 +582,7 @@ void
g_thread_init_glib (void)
{
static gboolean already_done;
- GRealThread* main_thread;
+ GRealThread *main_thread;
if (already_done)
return;
@@ -948,7 +948,8 @@ g_thread_new_internal (const gchar *name,
{
GRealThread *result;
GError *local_error = NULL;
- g_return_val_if_fail (func, NULL);
+
+ g_return_val_if_fail (func != NULL, NULL);
result = g_new0 (GRealThread, 1);
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]