Front page | perl.perl5.porters |
Postings from June 2012
On Sun, Jun 10, 2012 at 1:46 PM, Dave Mitchell <davem@iabyn.com> wrote: > It's generally known that perl has a lot of arbitrary 32-bit restrictions, > both in the code, and in the API; and that attempts to fix the former are > often hampered by the restrictions of the latter. > > $ grep '^A' embed.fnc | grep 32 | wc -l > 252 > > Perhaps its time to bite the bullet and give perl a whole new 64-bit-clean > API? For example, an av_fetch64() with IV rather than I32 args. > > Initially these might just be wrappers around the existing functions > which croak for args > 2^31; but eventually over time as internals get > written to be 64-bit clean, then instead the old functions become wrappers > around the new. > > Providing a completely new API might also give use the opportunity to > clean up other aspects of the API, not just 64-bit issues. > > Or perhaps XS code could just have > > #define USE_64BIT_API Is there a way to have a API which is independent of the pointer or word size? Just asking because the first supercomputers with 128bit address space (128bit virtual, 72bit physical for NECSX) will hit the market in 2013/2014. JoshThread Previous | Thread Next