Re: Re: 64bit and phpng, votes and plans

From: Date: Wed, 21 May 2014 06:04:19 +0000
Subject: Re: Re: 64bit and phpng, votes and plans
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14  Groups: php.internals 
Request: Send a blank email to internals+get-74400@lists.php.net to get a copy of this message
On 21/05/14 01:05, Rasmus Lerdorf wrote:
On 5/20/14, 4:56 PM, Lester Caine wrote:
On 20/05/14 23:57, Rasmus Lerdorf wrote:
So let's not assume that just because one segment of the userbase screams the loudest that this segment is representative. We have a large and diverse userbase and we need to make balanced decisions.
Handling BIGINT variables as a single 64bit number rather than as a string of characters would seem to be the more productive way of working, but is incompatible with 32bit platforms? It's working out exactly which path is the most productive which is the current question. If a 64bit integer is supported as a native variable, would it be practical to have it available on a 32bit platform? Having potentially to have to code for two different scenarios is not the best way of moving forward?
That has absolutely nothing to do with 64-bit string offsets which is what we are discussing here.
But integer is wrapped up in the very same RFC ... and the handling of that is just as important ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

Thread (29 messages)

« previous php.internals (#74400) next »