Lukas Kahwe Smith wrote:
On 19.03.2009, at 20:37, Rasmus Lerdorf wrote:
So, what is the final conclusion on this one? Are we at a combination
of Matt's and Dmitry's patches here?
I think we definitely need to fix this even in the 5.2 branch and get it
back to 5.1.x and earlier behavior. I consider it a bug that:
$arr[3500000000] = 'blah';
print_r($arr);
results in:
[-2147483648] => blah
if someone has written brand new 5.2-specific code that relies on this
weird behavior, then we will just have to bite the bullet and break that
code. It is way more likely that people are relying on the earlier
behavior and will end up with subtle problems in 5.2. I just had
someone at Yahoo get bitten by this when they upgraded from 5.1.x to
5.2.x.
If I understood it properly, the issue Matt/Dmitry are working on is
something else. So where do we stand on the issue Rasmus's notes (is
there a ticket for this one already)?
It's related to another Matt's proposal which cares about float to long
conversion.
Matt, what will we get with your patch and code above?
[LONG_MAX] => blah?
Thanks. Dmitry.
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
