Re: u/int64 support for glib status?

[Owen Taylor <otaylor redhat com>]

vishnu pobox com writes:

> What is the general feeling about:
> 
>   http://bugzilla.gnome.org/show_bug.cgi?id=59254

I don't have a huge opinion on this subject, since I'm probably
never going to use 64 bit ints, and certainly not for GValue :-)

One issue we have here is that if we did this, we'd basically probably
want to make int64 support mandatory ... I don't see extending the
hunk of API we have conditionalized with G_HAVE_GINT64.

Now, I suspect the vast majority of compilers used on Unix either have
compiler support for long long because they are GCC, or because they
are recent. I don't have any particular stats on this, however.

What about windows compilers? Do MSVCC and the Borland compiler
support a 64bit long long?

I put in on the future milestone because:

 - As long as gint64 is conditionalized, apps are going to have
   trouble depending on it.
 - It's something that can be later without compatibility problems
 - I don't see it as a real pressing API lack compared to other
   issues we have.
 - The more stuff we can _not_ put in 2.0.0, the happier I am :-)

But if there is a strong feeling we should put such support in, I'm
not going to raise a huge fuss. Just as long as we quickly resolve it
one way or the other. Tim?

Regards,
                                        Owen