Re: Re: 64bit and phpng, votes and plans
| From: | Rasmus Lerdorf | Date: | Wed, 21 May 2014 00:05:43 +0000 |
| Subject: | Re: Re: 64bit and phpng, votes and plans | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74396@lists.php.net to get a copy of this message | ||
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.
-Rasmus
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc