Re: G_TYPE_INT64
- From: Tim Janik <timj gtk org>
- To: Owen Taylor <otaylor redhat com>
- Cc: Gtk+ Developers <gtk-devel-list gnome org>
- Subject: Re: G_TYPE_INT64
- Date: Thu, 4 Oct 2001 14:02:34 +0200 (CEST)
On 4 Oct 2001, Owen Taylor wrote:
> > > > this is not an int64 fundamental type implementation, it just
> > > > implements a param spec for it, as i outlined in my original
> > > > commentary on matthieus patch.
> > >
> > > Well, the difference is not big and it's not hard to fix up.
> >
> > eh? the patch like you posted it is fundamentally broken in that
> > it specifies a fundamental type for INT64 and UINT64 but never registered it.
> > there's no point in comitting this before an actuall fundamental type
> > implementation is actually there. that's just like committing
> > void gtk_widget_foo (void);
> > void gtk_widget_bar (void);
> > void gtk_widget_baz (void);
> > one day without actual implementations.
>
> Basically, the situation is pretty simple:
>
> - No code for int64 support in gobject in CVS, no progress.
> - Code for int64 support in gobject in CVS, can be fixed.
>
> This not being something that I have much code around to test,
> and since you were not around, I decided that the best
> way of proceeding was to commit what we had, which was on
> examination correct at least as far as it went, and to let
> people tell me what was missing.
well the part that's there is unusable without the actual fundamental type
being implemented.
> > > > though, i thought we figured that 64bit ints are available
> > > > everywhere we run nowadays, so we should prolly simply require that
> > > > in configure.in.
> > >
> > > I don't see any particular point in that - read above.
> >
> > what above? the quote again? i certainly read that, my question
> > remains though. what's the point in special casing 64bit nowadays?
> > we've had a huge thread on that, and unless i actually see someone
> > telling me they have no 64bit type whatsoever, i'd rather require
> > it and have people provide build fixes for systems where 64bit ints
> > are not named long long.
>
> The quote was:
>
> > > > > - The support is conditionlized on the idea that if you don't have int64
> > > > > support, there is nothing you can do about it, so we might as
> > > > > well allow you to build the parts of GLib you can.
> > > > >
> > > > > (This is different from something like iconv() or gettext() where
> > > > > you can install an additional library to get the functionality.)
>
> There was a long thread which didn't seem particularly conclusive -
> conditionalizing was easy. So I did it.
ok, that's where CVS is now. lemme phrase this more clearly:
do you object to requirering 64bit ints as long as we don't come across
a platform that has no provisions for implementing such a thing?
>
> Regards,
> Owen
>
---
ciaoTJ
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]