On 03/02/15 22:35, Andrea Faulds wrote: >> Currently we have a problem with the size of integers, but simply >> > ignoring that there are limits is not the may to fix that problem. > This RFC doesn’t ignore that there are limits. Arbitrary-precision integers > are, naturally, bounded by available RAM (including the request memory limit).
BUT the whole problem currently IS the crap way 32bit integers roll over to float. And trying to handle 64bit integers currently on PHP IS a problem because of it. The current easy fix is simply to ignore the top 32 bits of BIGINT, but that solution is no longer practical with the growing volume of data we are handling. If I could ignore the 32bit builds then I would and then all that is required is something to switch off rolling out of the 64 bit integer and only support 64bit servers, but the remote machines are all going to be 32bit. It is ignoring the limitations of hardware that cause problems and while it may seem simple to 'do everything in abstract software' at some point just how the hardware is affecting the results comes into play. If you are going to add this abstract integer type, then it is equally important that the model also includes ranging, and length management so that things like bit wrapping work as expected. strict types should know that only an integer of a certain range is acceptable otherwise we have to add THAT at the library level. -- 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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
