dbus glib bindings: deriving from G_TYPE_BOXED, parameterized types

Colin Walters walters at verbum.org
Mon May 16 14:42:11 PDT 2005

On Mon, 2005-05-16 at 07:35 -0700, Dave Benson wrote:

> "List promises you to store arbitrary objects"..
> How does memory management work?  How does the client
> check the type of elements in the list?

If the client knows the GType of the list, then with a suitable API like
the one I proposed it can determine the element GType.

> It seems like you'd want a List<GValue> for that...

Well, you don't need the list to actually store GValues, but you do need
a GValue-ified interface to the list.  I started on that in my patch
with an API to iterate over a collection or map, with their values
marshalled to GValues.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.freedesktop.org/archives/dbus/attachments/20050516/2fb34418/attachment.pgp

More information about the dbus mailing list