Re: array_key_exists BC break
| From: | Alexey Zakhlestin | Date: | Fri, 24 Oct 2008 09:15:26 +0000 |
| Subject: | Re: array_key_exists BC break | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-41356@lists.php.net to get a copy of this message | ||
On Fri, Oct 24, 2008 at 1:05 PM, Ionut Gabriel Stan
<ionut.g.stan@gmail.com> wrote:
> But wouldn't be useful to at least accept objects implementing ArrayAccess?
sounds like a good idea to me
>
> On 10/23/2008 23:40, Mark van der Velden wrote:
>>
>> Stanislav Malyshev wrote:
>>
>>>
>>> Hi!
>>>
>>> I notice that 5.3 differs from 5.2 in how array_key_exists treats
>>> objects. In 5.2, if the second parameter (array) is allowed to be object
>>> and HASH_OF is applied to it. However, in 5.3 it would produce a warning
>>> requiring an array if object passed to it. Was it intentional?
>>> Maybe the problem is deeper and is in zend_parse_arg_impl where it
>>> should allow objects for 'a' if we can have HASH_OF from them?
>>>
>>
>> To my understanding, it's superseded by the function property_exists.
>> Also notice the difference of argument order.
>>
>> As written here: http://docs.php.net/array_key_exists
>>
>>
>>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Alexey Zakhlestin
http://blog.milkfarmsoft.com/