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
On Sun, 2009-06-21 at 19:33 -0500, Daniel Espinosa wrote:
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
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
On Sun, 2009-06-14 at 02:30 -0500, Daniel Espinosa wrote:
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.
Great, another library that registers its own GError boxed type. I think
I've
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
