On Fri, Nov 18, 2011 at 5:37 PM, Felipe Pena wrote:
> 2011/11/18 Etienne Kneuss :
>> To me, it feels similar to the Array->String conversion:
>> It is one of those implicit conversions that is almost always indicating a
>> bug.
>>
>> Therefore I would rather have both throw warnings than none of
2011/11/18 Etienne Kneuss :
> Hi,
>
> On Fri, Nov 18, 2011 at 16:41, Nikita Popov wrote:
>> *push*
>>
>> On Fri, Nov 11, 2011 at 10:40 PM, Nikita Popov
>> wrote:
>>> Hi internals!
>>>
>>> I'd like to get some attention to bug #60039 [1]. It is about the
>>> behavior of array_key_exists with "unus
Hi,
On Fri, Nov 18, 2011 at 16:41, Nikita Popov wrote:
> *push*
>
> On Fri, Nov 11, 2011 at 10:40 PM, Nikita Popov
> wrote:
>> Hi internals!
>>
>> I'd like to get some attention to bug #60039 [1]. It is about the
>> behavior of array_key_exists with "unusual" keys like floats, bools
>> and resou
*push*
On Fri, Nov 11, 2011 at 10:40 PM, Nikita Popov
wrote:
> Hi internals!
>
> I'd like to get some attention to bug #60039 [1]. It is about the
> behavior of array_key_exists with "unusual" keys like floats, bools
> and resources. Currently array_key_exists throws a warning if such a
> key is