Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41356 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45363 invoked from network); 24 Oct 2008 09:15:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Oct 2008 09:15:30 -0000 Authentication-Results: pb1.pair.com header.from=indeyets@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=indeyets@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.227 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: indeyets@gmail.com X-Host-Fingerprint: 209.85.198.227 rv-out-0506.google.com Received: from [209.85.198.227] ([209.85.198.227:1915] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3E/1E-01351-03291094 for ; Fri, 24 Oct 2008 05:15:29 -0400 Received: by rv-out-0506.google.com with SMTP id g37so815407rvb.23 for ; Fri, 24 Oct 2008 02:15:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=DNUgRGG5QF8VHDEvX97rW/uMjuDnXyeQsruSJ21p7lo=; b=xX6Z1vIwP18e0tUnBoCnhhUSMcfKMIL1B1gVC+wlnC4FJNPVBo3aq27Vbu21Hc/mIV grkWaNcYJKpMg7NH1H7bTR87/wh4pNc5exlNRapjm5A+qBDadVXSavFrWB/mSvd7cZ9o QpLBNTLyhkGIvCWfsOE7pMRlx/bt46qBUHSU0= 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=JyBOOl1XbqNnMK7nf6TSaKofvX/cbs3hIsRtXktT195h/gPiG++ZP6tcxifG+llKq0 Ozo+R3Ygk5u2YWrqvsSWdjhipdqCnZfqL0SdNisl7cs9VhUxj9dVq2xJambwxsllRhmV zu/JACtF8ybTCGTd4QQAMl8jZlF9qMeR9Byg4= Received: by 10.141.69.1 with SMTP id w1mr1020192rvk.185.1224839726206; Fri, 24 Oct 2008 02:15:26 -0700 (PDT) Received: by 10.140.133.15 with HTTP; Fri, 24 Oct 2008 02:15:26 -0700 (PDT) Message-ID: Date: Fri, 24 Oct 2008 13:15:26 +0400 To: "Ionut Gabriel Stan" Cc: "Mark van der Velden" , "Stanislav Malyshev" , "PHP Internals" In-Reply-To: <49018FC3.90302@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4900DB81.4000805@zend.com> <4900E150.1010607@dynom.nl> <49018FC3.90302@gmail.com> Subject: Re: [PHP-DEV] array_key_exists BC break From: indeyets@gmail.com ("Alexey Zakhlestin") On Fri, Oct 24, 2008 at 1:05 PM, Ionut Gabriel Stan 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/