[glib] Clarify GInitable docs



commit 626f197ee328c9b8ce11439e99b66fef14c5f9da
Author: Matthias Clasen <mclasen redhat com>
Date:   Mon Feb 7 23:35:21 2011 -0500

    Clarify GInitable docs
    
    Mention explicitly that the object is unrefed on error.
    Pointed out by Philip Van Hoof,
    https://bugzilla.gnome.org/show_bug.cgi?id=641363

 gio/ginitable.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/gio/ginitable.c b/gio/ginitable.c
index 0fdbe76..71da94e 100644
--- a/gio/ginitable.c
+++ b/gio/ginitable.c
@@ -43,7 +43,8 @@
  * in various ways. For C applications you generally just call
  * g_initable_new() directly, or indirectly via a foo_thing_new() wrapper.
  * This will call g_initable_init() under the cover, returning %NULL and
- * setting a %GError on failure.
+ * setting a #GError on failure (at which point the instance is
+ * unreferenced).
  *
  * For bindings in languages where the native constructor supports
  * exceptions the binding could check for objects implemention %GInitable



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