That's true, but is there any data type check when g_object_set/get function is called?
If GLib plans to use G_TYPE_POINTER for GSList, GError, gshort, and any other data type without G_TYPE* macro defined, then just tell it on the documentation: "if you (programer) want to use a not defined type use G_TYPE_POINTER on properties declaration". If documented or the better practice is stablished, some projects like Anjuta doesn't need to define a G_TYPE_ERROR from him self. 2009/6/17 Owen Taylor <otay...@redhat.com> > On Sun, 2009-06-14 at 02:30 -0500, Daniel Espinosa wrote: > > How to handle data types without a GLib GType defined. > > > > On libgda, it define a GType for GError and a GSList becouse these > > doesn't exist on GLib and it uses them as parameters when creating > > properties and events. > > > > For now may be the library (as Anjuta does) must create its own GType > > definition but with the following rule: the name of the type must be > > defined as "GError" and "GSList", in order to allow g-ri-scanner to > > detects the currect types GError and GSList as the example. > > > > In GDA it has GDA_TYPE_ERROR and GDA_TYPE_SLIST with "GdaError" and > > "GdaSList", then the scanner tries to find a definition to GdaError > > and GdaSList but they don't exist, when changed this types' names as > > avobe the correct type is detected. > > To point out what may be obvious - there is zero advantage of a > <X>_TYPE_SLIST over G_TYPE_POINTER. > > This is true in general, and true for gobject-introspection - if > gobject-introspection finds a property by introspection and deduces a > type of GSList for it, it still doesn't have the element-type. > > - Owen > > > -- Trabajar, la mejor arma para tu superación "de grano en grano, se hace la arena" (R) (en trámite, pero para los cuates: LIBRE)
_______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-devel-list
