Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41350 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34533 invoked from network); 23 Oct 2008 21:14:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Oct 2008 21:14:49 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 212.25.124.163 il-gw1.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.163] ([212.25.124.163:48785] helo=il-gw1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 13/B4-44135-849E0094 for ; Thu, 23 Oct 2008 17:14:49 -0400 Received: from us-ex1.zend.com ([192.168.16.5]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Oct 2008 23:15:13 +0200 Received: from [192.168.16.110] ([192.168.16.110]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 23 Oct 2008 14:15:10 -0700 Message-ID: <4900E95E.7060103@zend.com> Date: Thu, 23 Oct 2008 14:15:10 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Mark van der Velden CC: 'PHP Internals' References: <4900DB81.4000805@zend.com> <4900E150.1010607@dynom.nl> In-Reply-To: <4900E150.1010607@dynom.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Oct 2008 21:15:10.0455 (UTC) FILETIME=[6E85B070:01C93554] Subject: Re: [PHP-DEV] array_key_exists BC break From: stas@zend.com (Stanislav Malyshev) 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. Ah, ok, missed this note, thanks. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com