Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41357
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.78.25 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=TcBv6YM/d6I2MskiQknEL7Tq2EhcGkIK+e5JPi/ymLXpzY0a+QOlwSHW2AexCgVIbH
         O19/joYrGX4PbF3Pd9Qj/wfsFSHxJE/pIMUyF8DUzfMmqI+4D+ex5gGNdBSY/ZxIxOKe
         po9QrH7SNoJCJzdlSKIGLxWC6H25bQ8RHYme8=
Message-ID: <46ccd1ab0810240306l2e68c1f9l5e1075dbe59bd19d@mail.gmail.com>
Date: Fri, 24 Oct 2008 08:06:05 -0200
To: "Stanislav Malyshev" <stas@zend.com>
Cc: "Mark van der Velden" <mark@dynom.nl>, 
	"PHP Internals" <internals@lists.php.net>
In-Reply-To: <4900E95E.7060103@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <4900DB81.4000805@zend.com> <4900E150.1010607@dynom.nl>
	 <4900E95E.7060103@zend.com>
Subject: Re: [PHP-DEV] array_key_exists BC break
From: felipensp@gmail.com ("Felipe Pena")

Hi Stas,

2008/10/23 Stanislav Malyshev <stas@zend.com>:
> 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 objec=
t
>>> and HASH_OF is applied to it. However, in 5.3 it would produce a warnin=
g
>>> 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.
>
> Ah, ok, missed this note, thanks.

In fact, all HASH_OF was removed in standard/array.c, and that's
already is mentioned implicitly though, as
"The functions next()/current/=85 don't take objects anymore as
parameters. For accessing their properties using this way you have to
cast the objects to arrays first."

--=20
Regards,
Felipe Pena.