Mike, I took a look into gtkd sources, trying to make simple clutter bindings and found that gboolean is int (as expected), but in function declarations instead of gboolean int is used explicitly. Is it intended?
On 11/30/2013 08:35 AM, Alexandr Druzninin wrote:
Mike, I took a look into gtkd sources, trying to make simple clutter bindings and found that gboolean is int (as expected), but in function declarations instead of gboolean int is used explicitly. Is it intended?
Just never got around to changing it.
On Sat, 30 Nov 2013 17:54:39 +0100, Mike Wey wrote:
On 11/30/2013 08:35 AM, Alexandr Druzninin wrote:
Mike, I took a look into gtkd sources, trying to make simple clutter bindings and found that gboolean is int (as expected), but in function declarations instead of gboolean int is used explicitly. Is it intended?
Just never got around to changing it.
I mean gtkc.glibtypes module, for example GOptionParseFunc function returns int instead of gboolean. I guess it may be because gboolean is defined in the same module?
On 11/30/2013 09:38 PM, Alexandr Druzninin wrote:
I mean gtkc.glibtypes module, for example GOptionParseFunc function returns int instead of gboolean. I guess it may be because gboolean is defined in the same module?
The wrapper turns most of the basic glib types to there D equivalent.