[gegl] gegl: Clarify that gegl_processor_destroy() will always only unref
- From: Martin Nordholts <martinn src gnome org>
- To: svn-commits-list gnome org
- Cc:
- Subject: [gegl] gegl: Clarify that gegl_processor_destroy() will always only unref
- Date: Sun, 10 Jan 2010 17:32:33 +0000 (UTC)
commit 3bd64469cf6713462f072a33ff02d5d527e17632
Author: Martin Nordholts <martinn src gnome org>
Date: Sun Jan 10 18:33:39 2010 +0100
gegl: Clarify that gegl_processor_destroy() will always only unref
gegl/process/gegl-processor.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
---
diff --git a/gegl/process/gegl-processor.c b/gegl/process/gegl-processor.c
index 5c96e3e..be90881 100644
--- a/gegl/process/gegl-processor.c
+++ b/gegl/process/gegl-processor.c
@@ -744,6 +744,11 @@ gegl_processor_work (GeglProcessor *processor,
void
gegl_processor_destroy (GeglProcessor *processor)
{
+ /* The only thing this function is doing is shielding users of the
+ * library from GLib. If you are writing a language wrapper you can
+ * use the normal GObject unreffing mechanisms. This function will
+ * never do more than unreffing the processor.
+ */
g_object_unref (processor);
}
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]