-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Manish Singh wrote: | Actually, the common idiom is to define: | | parent_class = g_type_class_peek_parent (class); | | in class_init, with parent_class being a static at file scope. Then you just | use it as Calvin did whenever you need to chain up. Less code clutter that | way. so this: "The problem here is how we can find the parent constructor. An approach (used in GTK+ source code) would be to save the original constructor in a static variable from maman_bar_class_init and then to re-use it from maman_bar_constructor. This is clearly possible and very simple but I was told it was not nice and the prefered way is to use the g_type_class_peek and g_type_class_peek_parent functions." from this: http://www.le-hacker.org/papers/gobject/ch04.html#gobject-instanciation is wrong? - -- Dan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/97F3ad4P1+ZAZk0RAs5WAJ0StC4kAiOZQ9Zh85vYUXt+WZHuQACdFO80 lgM4EyslwwHMKoulJy29CGw= =rubT -----END PGP SIGNATURE-----
