RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

gegl_node_set_property

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
gegl_node_set_property Florent Monnier 26 Jun 21:14
  gegl_node_set_property Martin Nordholts 26 Jun 22:11
Florent Monnier
2009-06-26 21:14:49 UTC (over 15 years ago)

gegl_node_set_property

Hi,
I have a question about the use of the type GValue for the function gegl_node_set_property(). As I'm not familiar with the glib, I have read the doc and used g_value_unset() at the end. But then I've read the source of the python and ruby bindings and seen g_value_unset() was not used, so what is the correct use? isn't there a memory leak without g_value_unset() ?

Martin Nordholts
2009-06-26 22:11:16 UTC (over 15 years ago)

gegl_node_set_property

Florent Monnier wrote:

Hi,
I have a question about the use of the type GValue for the function gegl_node_set_property(). As I'm not familiar with the glib, I have read the doc and used g_value_unset() at the end. But then I've read the source of the python and ruby bindings and seen g_value_unset() was not used, so what is the correct use? isn't there a memory leak without g_value_unset() ?

After looking briefly at the ruby binding it also looks like a leak to me. Yes, one need to call g_value_unset() on used GValue:s, otherwise there is a risk of memory leaks.

BR, Martin