dseguy, 5 months ago

An array is full when there are no more available index. When appending, #PHP creates the next index by adding 1 to the current maximum one.

So start with PHP_INT_MAX as a key, use an append and you'll get the error.

https://3v4l.org/lvj9d

SenseException, 5 months ago

@dseguy The #php error message is really weird. I'd expect a message similar to #SplFixedArray.
https://3v4l.org/9p1Hr

dseguy, 5 months ago

@SenseException Yes, this makes more sense when one read it.

lewiscowles1986, 5 months ago

@dseguy what are folks doing wrong, if they are storing arrays of PHP_INT_MAX size?

Much beyond 10,000; I'd start to ask more impatiently, if maybe, perhaps it might be more appropriate to deal with algorithms and structures; designed for that volume of data.

dseguy, 5 months ago

@lewiscowles1986 I agree when reaching that level, on a 64bits machine 😨 , there must be other problems that will pop up before.

The error message is amusing, I think.

arnan, 5 months ago

@dseguy Should've used array_push. It adds things to the end 🤣
(Dunno if that's a real fix)

dseguy, 5 months ago

@arnan Worth a try, but same error.

#PHP is trying to make those features with different syntax, homogenous. You may still find some missed opportunities, so it's important to check them.

alessandrolai, 5 months ago

@dseguy array access to a readonly property?

dseguy, 5 months ago

@alessandrolai Nice try. Readonly has precedence in this case, and it yields another crytpic message :

'Cannot indirectly modify readonly property x::$array'

https://3v4l.org/a6qTd

merms, 5 months ago

@dseguy Googled it because I wanted to know if I could realistically have figured it out. I feel dumb now.

dseguy, 5 months ago

@merms With the answer in hand, I think the message might be more explicit.