Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74289
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender)
Content-Type: text/plain; charset=koi8-r; format=flowed; delsp=yes
To: internals@lists.php.net
References: <CAF+90c8m8kMNjHOOKWs3iTxnLSVv41pk0mGjgzvvp2+Lieh+ig@mail.gmail.com>
Date: Sat, 17 May 2014 23:01:56 +0400
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Message-ID: <op.xf0ptinpc9evq2@nikita-pc>
In-Reply-To: <CAF+90c8m8kMNjHOOKWs3iTxnLSVv41pk0mGjgzvvp2+Lieh+ig@mail.gmail.com>
User-Agent: Opera Mail/12.17 (Win32)
Subject: Re: [PHP-DEV] Rethinking 64bit sizes and PHP-NG
From: inefedor@gmail.com ("Nikita Nefedov")

On Sat, 17 May 2014 22:27:02 +0400, Nikita Popov <nikita.ppv@gmail.com>  
wrote:

> Hi internals!
>
> The discussions around the patch for improved 64bit support have
> deteriorated from a semi-reasonable discussions to pointless accusations
> and name-calling. I'd like to get back to discussing this issue from a
> technical point of view and see which parts of the patch can be salvaged
> and which can not.


Hey,

First thank you for arranging all this points.

I just wanted to ask: could we also make nNextFreeElement be unsigned?  
Because with your proposal it would be possible to overflow it with the  
code like this: $array[pow(2, 32) + 1] = 123; (if I understand it  
correctly)

And besides that we can't have negative keys anyway.