GObjectification - GSoC progress as of June 16, 2013

Mark Doliner mark at kingant.net
Thu Jun 27 03:39:08 EDT 2013

On Tue, Jun 18, 2013 at 8:22 PM, Ethan Blanton <elb at pidgin.im> wrote:
> This has several implications, but they all basically boil down to the
> fact that the *subclass* has to know the size of the parent class.
> Having to know the size means it can't be hidden.  Having to know the
> size and maintaining linkage compatability means it can't change size.
> So ... we're back where we started.

Do we generally want our GObjects to be subclassable? I guess the
benefit is that plugins have more power to alter our behavior? And the
downside is that we have to be more careful not to break API?

What do other GObject-based programs do? Or glib itself? Or GTK+?

More information about the Devel mailing list