From 626f197ee328c9b8ce11439e99b66fef14c5f9da Mon Sep 17 00:00:00 2001 From: Matthias Clasen Date: Mon, 7 Feb 2011 23:35:21 -0500 Subject: [PATCH] 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 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gio/ginitable.c b/gio/ginitable.c index 0fdbe767c..71da94e27 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