Re: Problems with signals and object destruction
- From: Christian Borup <borup borup com>
- To: Daniel Kasak <dkasak nusconsulting com au>
- Cc: gtk2-perl List <gtk-perl-list gnome org>
- Subject: Re: Problems with signals and object destruction
- Date: Fri, 20 Apr 2007 11:47:50 +0200
On Fri, 2007-04-20 at 13:48 +1000, Daniel Kasak wrote:
This sort of gymnastics should not be necessary. GObject will
destroy all of its signal handlers in the base GObject::dispose()
method (part of the destruction process), and Glib::Object connects
those with closures so that we get proper destruction notification
for cleaning up the callback subroutine and user data references.
With that, and reference counting everywhere, everything should Just
The situations you want to watch out for are:
- Any form of circular reference. Avoid keeping references to yourself.
Doh! In Gtk2::Ex::Datasheet::DBI I'm creating circular references so
that TreeViewColumns have access to the definition used to set them up.
I was wondering if this would create problems ... certainly EPIC (
Eclipse Perl debugger ) doesn't like it. I'll come up with a less dodgy
way of packing info into TreeViewColumns.
Anyway, I'll look into getting rid of those circular references.
You could just weaken the reference, using weaken from Scalar::Util.
That should keep your objects from leaking, without major surgery on you
] [Thread Prev