Re: [Chicken-users] long pointer equivalent

[Perry E. Metzger]

Peter Keller <address@hidden> writes:
> See, the trouble is with a specific 64 bit type is how do you deal with
> machines that happen to define that library call where an off_t is a
> 32-bit type? long on an ia64 is 8 bytes, but on an ia386 is 4 bytes, 
> therefore you may not use an unsigned-int64 as the interface call to
> lseek because it isn't right all of the time.

I'd say autoconf style mechanisms are the only way to retain sanity
for such things. When you build the chicken runtime for a particular
platform, you find out what the width is and you abstract that in
the library so it uses the discovered value.


-- 
Perry E. Metzger                address@hidden
--
"Ask not what your country can force other people to do for you..."