Re: non-64bit platforms? (Re: g[u]int64 GValues (was GValue questions))

[Tim Janik <timj gtk org>]

On Mon, 13 Aug 2001, Johannes Stezenbach wrote:

> Pavel Machek wrote:
> > 
> > > > > right, but afaik, 64bit ints are not supported on all system/compiler versions
> > > > > that glob runs on. at least historically this has been an issue, which is why
> > > > > we special-case guint64 definitions in glib based on a configure.in check.
> > > > > i'm not quite sure where 64bit ints fail nowadays though, irrc, orbit
> > > > > has a hard dependancy on 64bit ints for quite some time now and runs on a
> > > > > bunch of systems.
> > > >
> > > > Midnight commander (even text edition) depends on glib, and it really
> > > > wants to be portable to obscure systems... Try to ask on mc-devel if
> > > > all platforms do have 64-bit integers...
> > >
> > > All**1 platforms with gcc do. And practicly all 'long long' using code out
> > > there relies on it being 64 bits, so it's unlikely that gcc ports would
> > > use some other size for it.
> > 
> > I'm afraid that mc is use even on platforms that lack gcc... This
> > still might be a problem.
> 
> To summarize: If glib wants to support mc on all platforms, glib can't
> have unconditional 64-bit int support.

i don't second that summary, so far i have just seen vague hints towards
"glib might be used on platforms that don't have 64bit ints" but not 
seen a single example posted.

i'm currently leaning towards requirering 64bit int in configure.in
untill i see at least one report that we need to conditionalize this.

if that means that one glib version is broken on such a platform, well,
we've had worse releases and can fix it pretty quickly. at least we're not
coding around a phantom anymore (and that's what non-64bit hints are to
me untill i see a single platform stated).

> 
> Regards,
> Johannes
> 

---
ciaoTJ