Hi,
The mark fonction for GLib::Object retrieves all properties on an
object to
potentially mark them. While it will only actually mark them if it’s
another
object.
Which if ofcourse kinda wastefull… Attached patch changes the mark
function
to only retrieve the object property if it’s a GObject… Ok to commit
?
I was wondering why it’s even the case that object which are
accessible
through GObject properties are marked? Is it just to try to keep the
holder
struct attached as long as we can see an easy way to get the object ?
Sjoerd
Hi Sjoerd,
On Thu, 8 Jun 2006 01:11:00 +0200
[email protected] (Sjoerd S.) wrote:
Hi,
The mark fonction for GLib::Object retrieves all properties on an object to
potentially mark them. While it will only actually mark them if it’s another
object.
Which if ofcourse kinda wastefull… Attached patch changes the mark function
to only retrieve the object property if it’s a GObject… Ok to commit ?
OK, Apply it, please.
I was wondering why it’s even the case that object which are accessible
through GObject properties are marked? Is it just to try to keep the holder
struct attached as long as we can see an easy way to get the object ?
This aims to fix GC problems. The children of Gtk::Container and
the properties of GLib::Object are managed correctly from ruby side.
–
.:% Masao M.[email protected]