Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

Hi,

well, I checked the manual (even in other languages). But if I missed something essential let me know.

What I wanted to point out is, that the manual says integers are converted to float if an integer overflow is encountered. (See: http://www.php.net/manual/en/language.types.integer.php at section "Integer overflow")

Furthermore the manual says about using arrays if when no index is given the array generates itself an index to use. (See: http://www.php.net/manual/en/language.types.array.php at section "Creating/modifying with square bracket syntax") It says: "As mentioned above, if no key is specified, the maximum of the existing integer indices is taken, and the new key will be that maximum value plus 1."

So what happens when this maximum value is already MAX_INT ? It then is not converted to float and if so, it would then be truncated to integer ... and then the integer overflow comes across.

Again, the manual says "the MAXIMUM of the existing integer indices ... is taken" and that's just not true for the code I provided in the first post and the one down below.

Here's another code sample to show:

<?php
$max_int = 2147483647; // Max integer value on a 32-bit system
$arr     = array();

$arr[]           = 'some';
$arr[ $max_int ] = 'values';
$arr[]           = 'another'; // The max of int indices is taken +1 for this key/index
$arr[]           = 'value'; // This should be the same index as for value 'another' as max_int is the maximum integer indice in the array. But it doesn't happen.

print_r( $arr );

?>

Which prints:
Array
(
    [0] => some
    [2147483647] => values
    [-2147483648] => another
    [-2147483647] => value
)


Regards,
Marcel

Your initial report is technically correct, as far as what's happening internally, and the second example shows it -- the initial example would too if this line is commented/removed:

$arr[1] = 'one'; // New index: 2

Otherwise, this is a duplicate of Bug #47836, which is now fixed. The initial code will still give the same warning (I'm sure you expect that though), but for a different reason internally. :-)