[gst-devel] Why wrapping GLib interfaces?

Ramón García ramon_garcia_f at yahoo.com
Mon Oct 13 04:08:03 CEST 2003

You suggest that it is necessary to offer the
functionality of deciding inside each different object
whether to expose an interface or not.

Can you post a use case that shows that this is
useful? I  think that if different objects expose
different interfaces, they should belong to different
classes (though one can inherit from the other). The
only restriction that this enforces is that an object
cannot make the decission of exposing an interface
dynamically based on its state. However, in that case,
rather than "implementing" an interface, the object
"has got" or "has not got" something. Thus the class
of that object can have a function Interface*
getInterface() to get an instance of that interface,
which can return NULL. That should be different than
implementing an interface.


Yahoo! Messenger - Nueva versión GRATIS
Super Webcam, voz, caritas animadas, y más...

More information about the gstreamer-devel mailing list