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

From: Date: Tue, 20 May 2014 21:58:30 +0000
Subject: Re: Re: 64bit and phpng, votes and plans
References: 1 2 3 4 5 6 7 8 9 10  Groups: php.internals 
Request: Send a blank email to internals+get-74390@lists.php.net to get a copy of this message 
On 20/05/14 22:17, Stas Malyshev wrote:

64bit int if int is 64bit. I prefer consistency, so array int key is better

to support
64bit int key. IMHO.
Given that 99.9999% of PHP users will never need it, but 100% of PHP
users will pay in performance for each size increase, we need to be
careful here. "Consistency" is not more magic word than "security".


Consistency is the main problem here. Most database engines use 64bit unique identifiers for SEQUENCE values. Upgrading systems that have been using 32bit integer values for this to support 64bit ones is the problem I've been living with. 32bit client apps get a string value where previously it was a simple integer.


Similar argument applies to string also. It would be WTF, when users try to
access string offset over 32bit values. Data dealt with PHP is getting
larger
and larger. It would be an issue sooner or later.
Not likely, unless somehow PHP becomes language of choice for processing
big data. Which I don't see exactly happening. But if it ever happens,
we can deal with it then.


It is here today and has been for many years now. While the number of records may not be large, using large offsets can result in passing the 32bit boundary and what was an integer flips ...

-- 
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 (#74390) next »