Alan Burlison <[EMAIL PROTECTED]> writes: >Nick Ing-Simmons wrote: > >> >Nope. This code will run on 32-bit systems mostly (I've been running it on >> >x86 and PPC for testing purposes). Why is it that the Perl build scripts >> >generate headers with 'long long' typedef'd as Quad_t (or something like >> >that) but nothing seems to actually use that type? >> >> It is in case you configure to build a 64-bit perl. >> >> It is certainly possible to build a 64-bit perl on x86 - but is slower than >> a 32-bit perl as _ALL_ integer ops are done as long long (Quad_t). > >Note that '64 bit' is too loose a term to be useful in this context. It could >mean 'a perl built with a 64-bit address space (LP64)' or 'a perl built with >long long support'. It is possible to have a LP32 (i.e. 32-bit address space) >perl that supports 64-bit IVs. x86 will support the latter, but not the >former. Some other platforms will support both LP32 and LP64 perls, and some >will only support LP64.
Agree to all that. I was talking in terms of Configure's -Duse64bitint i.e. can a perl scalar hold a 64 bit value non-lossy? > >-- >Alan Burlison -- Nick Ing-Simmons http://www.ni-s.u-net.com/
