Re: GLib 64 bit integer problem revisited

[Jeff Franks <jcf tpg com au>]

Tim Janik wrote:

> On Mon, 18 Nov 2002, Owen Taylor wrote:
>
> >In hindsight, having both int/long and int64 for GValue is probably
> >a bad idea; it probably would have been better to just have int32
> >and int64... but not something we can change at this point.
>
>
> right, using longs as properties or signal arguments is a bad idea 
> anyways,
> so language bindings like C++ should simply use set/get (gint&) and 
> (gint64&)
> and skip longs entirely (internally, these may be passed on as TYPE_INT or
> TYPE_INT64 values to g_object_set_property(), the property system performs
> the necessary conversions if required).
> that is, unless there're compat reasons set/get (glong&) have to stay 
> in the
> C++ bindings.
I thought this would be the way to go. Thank you for letting me know. I 
just remove the glong and gulong get/set methods.

Regards,

Jeff Franks.