Re: g_object_ref_sink and GUnowned

2006-01-06 Thread Matthias Clasen
On 1/3/06, Torsten Schoenfeld [EMAIL PROTECTED] wrote: On Tue, 2006-01-03 at 14:32 +0100, Tim Janik wrote: GtkObject derives from GUnowned This breaks the Perl bindings of GTK+. Our GTK+ bindings register GtkObject with our GLib bindings at start up. This involves

Re: g_object_ref_sink and GUnowned

2006-01-01 Thread James Henstridge
Emmanuele Bassi wrote: Hi, On Wed, 2005-12-28 at 12:45 -0500, Havoc Pennington wrote: On Thu, 2005-12-22 at 19:02 +0100, Tim Janik wrote: in fact, there is no technical reason for this. so many people have argued this to be better though (havoc even went so far as to argue why this

Re: g_object_ref_sink and GUnowned

2005-12-31 Thread Torsten Schoenfeld
On Thu, 2005-12-22 at 17:49 +0100, Tim Janik wrote: GtkObject derives from GUnowned This breaks the Perl bindings of GTK+. Our GTK+ bindings register GtkObject with our GLib bindings at start up. This involves associating it with the namespace Gtk2::Object and it usually also means setting

Re: g_object_ref_sink and GUnowned

2005-12-31 Thread Emmanuele Bassi
Hi, On Wed, 2005-12-28 at 12:45 -0500, Havoc Pennington wrote: On Thu, 2005-12-22 at 19:02 +0100, Tim Janik wrote: in fact, there is no technical reason for this. so many people have argued this to be better though (havoc even went so far as to argue why this would be conceptually

Re: g_object_ref_sink and GUnowned

2005-12-31 Thread muppet
On Dec 31, 2005, at 7:56 AM, Emmanuele Bassi wrote: Hi, On Wed, 2005-12-28 at 12:45 -0500, Havoc Pennington wrote: On Thu, 2005-12-22 at 19:02 +0100, Tim Janik wrote: in fact, there is no technical reason for this. Not that it's all that relevant ;-) but I also thought a flag in the class

Re: g_object_ref_sink and GUnowned

2005-12-28 Thread Havoc Pennington
On Thu, 2005-12-22 at 19:02 +0100, Tim Janik wrote: in fact, there is no technical reason for this. so many people have argued this to be better though (havoc even went so far as to argue why this would be conceptually neccessary), that i decided to simply sponsor an object type if that helps

g_object_ref_sink and GUnowned

2005-12-22 Thread Tim Janik
changed CVS accordingly, so: - gtk+ = 2.8 + glib = 2.8 GObject is initially non floating; GtkObject is initially floating as always - gtk+ = 2.8.10 + glib = 2.10, GObject is initially non floating; GObject offers floating API: g_object_is_floating(), g_object_ref_sink

Re: g_object_ref_sink and GUnowned

2005-12-22 Thread Owen Taylor
On Thu, 2005-12-22 at 17:49 +0100, Tim Janik wrote: GUnowned derives from GObject, has intiially a floating ref_count. I hate to quibble names, but it seems really strange to have a class GUnowned where instances are normally owned. (In fact, the goal of anybody using a GUnowned has to be to

Re: g_object_ref_sink and GUnowned

2005-12-22 Thread Yevgen Muntyan
Tim Janik wrote: in fact, there is no technical reason for this. so many people have argued this to be better though (havoc even went so far as to argue why this would be conceptually neccessary), that i decided to simply sponsor an object type if that helps the majority to understand which

Re: g_object_ref_sink and GUnowned

2005-12-22 Thread Tim Janik
On Thu, 22 Dec 2005, Yevgen Muntyan wrote: Tim Janik wrote: in fact, there is no technical reason for this. so many people have argued this to be better though (havoc even went so far as to argue why this would be conceptually neccessary), that i decided to simply sponsor an object type if