Life of Glib::OptionEntry objects

2007-10-28 Thread Matt Bucknall
Hi, Do Glib::OptionEntry objects that have been added to a Glib::OptionGroup object get copied, or do they have to exist for as long as the Glib::OptionGroup object exists (in much the same way Glib::OptionGroup objects have to exist for the lifetime of a Glib::OptionContext object)? Thanks, M

Re: Chaining Up (GLib Tutorial Error)

2007-10-28 Thread Yevgen Muntyan
Stefan Kost wrote: > Yevgen Muntyan schrieb: > >> Phil Lello wrote: >> >>> According to the GObject tutorial, chaining-up in >>> constructor/dispose/finalize code should be handled as follows: >>> >>> static void >>> b_method_to_call (B *obj, int a) >>> { >>> BClass *klass; >>> AClass

Re: Chaining Up (GLib Tutorial Error)

2007-10-28 Thread Xan
On 10/28/07, Stefan Kost <[EMAIL PROTECTED]> wrote: > >> (Unless there is something horribly wrong with my implementation of > >> _GET_CLASS...) > >> > >> This works fine until we create CClass, a direct descendant of BClass. > >> When CClass is using the default 'method_to_call' code, e.g. in > >>

Re: Chaining Up (GLib Tutorial Error)

2007-10-28 Thread Stefan Kost
Yevgen Muntyan schrieb: > Phil Lello wrote: >> According to the GObject tutorial, chaining-up in >> constructor/dispose/finalize code should be handled as follows: >> >> static void >> b_method_to_call (B *obj, int a) >> { >> BClass *klass; >> AClass *parent_class; >> klass = B_GET_CLASS (ob