Re: Re: 64bit and phpng, votes and plans
| From: | Yasuo Ohgaki | Date: | Wed, 21 May 2014 05:46:02 +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-74398@lists.php.net to get a copy of this message | ||
Hi Nikita,
On Wed, May 21, 2014 at 2:21 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:
> As I have already said: 64bit (or rather 63bit) integer keys are already
> supported on LP64 and ILP64 platforms. This proposal supports them on LLP64
> as well. The issue you're hitting has nothing to do with 64bit integers -
> you are using a key that is *way* larger than that, i.e. a double key.
> Double keys are handled by converting them to integers frist. This
> conversion is a wraparound conversion, not a clamp conversion, so you end
> up with some meaningless negative number.
It was wrong example. However, if array int key size is 32bit, 64bit value
would never fit.
I agree Rasmus's argument about string offset. If anyone would
like to deal with extremely large data, they should use stream or like.
It just wouldn't work well without it now.
Regardless of this RFC acceptance or not, it's nice if all of these
limitations
are documented in the manual under single section. Perhaps, new
appendix?
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net