Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41477
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain caedmon.net from 64.15.79.181 cause and error)
Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>,
 Alexey Zakhlestin <indeyets@gmail.com>,
 Ionut Gabriel Stan <ionut.g.stan@gmail.com>,
 Mark van der Velden <mark@dynom.nl>,
 Stanislav Malyshev <stas@zend.com>,
 PHP Internals <internals@lists.php.net>
Message-ID: <B33D6ECB-9A18-4FCA-A2A5-B185CC6CE512@caedmon.net>
To: Andrei Zmievski <andrei@gravitonic.com>
In-Reply-To: <490609A1.7090400@gravitonic.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Mon, 27 Oct 2008 14:39:35 -0400
References: <4900DB81.4000805@zend.com> <4900E150.1010607@dynom.nl> <49018FC3.90302@gmail.com> <cd5680a20810240215t4d564ab6n4a397ff22166fa83@mail.gmail.com> <1224854888.19390.89.camel@goldfinger.johannes.nop> <490609A1.7090400@gravitonic.com>
Subject: Re: [PHP-DEV] array_key_exists BC break
From: sean@caedmon.net (Sean Coates)

>> btw. this also affects quite a few other functions: next/current/ 
>> key/...
>> at least ... and maybe more after using the "new" parameter parsing  
>> API.
>
> I would say "no" for 5.3. But for 6 it would be fantastic to have  
> all array-related operations supporting ArrayAccess interface, where  
> possible.

I was hoping someone would revive this thread (-:

In Habari, we have/had an ArrayObject that we passed to the view  
(theme). As far as the theme knows, this is an array (but it has extra  
methods if the theme is particularly smart).

Unfortunately, this breaks in 5.3, because many of the themes use  
reset() to get the first element of the array (ArrayObject, but the  
theme doesn't necessarily know this).

This is a real-world BC break, and without allowing ArrayObject to act  
like an array, it's nearly useless. We've temporarily "solved" this by  
casting the ArrayObject to an array, which is silly. This should be  
fixed in 5.3, IMO.

I discussed this with Johannes a bit, yesterday.

S