After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 585707 - How to handle data types without a GLib GType defined.
How to handle data types without a GLib GType defined.
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gobject
2.20.x
Other All
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2009-06-14 07:17 UTC by Daniel Espinosa
Modified: 2013-11-24 00:10 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Daniel Espinosa 2009-06-14 07:17:25 UTC
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.

If introspection is required then follow this 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. (For more info about GDA/GObject Instrospection see bug #585351).
Comment 1 Daniel Espinosa 2009-06-14 07:19:39 UTC
Adding that may ALL datatypes on GLib must have its own GType to help other libraries to use them directly with out define its self and avoid misstakes that prevents to have introspection.
Comment 2 Matthias Clasen 2013-11-24 00:10:46 UTC
GList and GSList should simply be treated as G_TYPE_POINTER. Many other GLib types have boxes type definitions in gobject now