Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41735
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.46.30 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=subject:from:to:cc:in-reply-to:references:content-type:date
         :message-id:mime-version:x-mailer:content-transfer-encoding;
        b=kfcL1jugA5TgT3/AE56rkx+jOUKugp4O6t4Avce2JEHnVLmnTN4L6cw5i8iyn5mJx0
         vSVYH6sE2fEk+OWzJYJdZ3Fzw6lyhCzG6H123eXS6325Qb0uUUJx+0TXN101qd43+0b2
         4sH6SiwKadTl3xU/2/pjDMlUyu/kGk4tyMdBM=
To: Stanislav Malyshev <stas@zend.com>
Cc: Geoffrey Sneddon <foolistbar@googlemail.com>, Lukas Kahwe Smith <mls@pooteeweet.org>, PHP Internals <internals@lists.php.net>
In-Reply-To: <49133302.4040701@zend.com>
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> <1225199800.878.0.camel@localhost>
	 <3F3445975B55414BB4A214B32E178657@pc>
	 <4A4FE9BC-F000-4AEE-A68C-8EFEA9DCD154@pooteeweet.org>
	 <4910D3E5.4020406@zend.com>
	 <237D5067-10C6-4D25-8CCF-FEF9FE44F6F6@googlemail.com>
	 <1225973406.5465.18.camel@felipe>  <49133302.4040701@zend.com>
Content-Type: text/plain; charset=utf-8
Date: Thu, 06 Nov 2008 16:29:13 -0200
Message-ID: <1225996153.5465.30.camel@felipe>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] array_key_exists BC break
From: felipensp@gmail.com (Felipe Pena)

Em Qui, 2008-11-06 às 10:10 -0800, Stanislav Malyshev escreveu:
> Hi!
> 
> > So as suggested and wished, here is a patch that add a modifier '%' to
> > 'a' in parameter parsing API, where it allows object that implements
> > ArrayAccess to be accept. Although it doesn't invoke any their methods,
> > i.e. just how it works nowdays.
> 
> I think if you use HASH_OF then any object having get_properties should 
> be fine... Is there any reason to restrict it to ArrayAccess?

Well, there is no reason, I was only following what was said.
It would make more sense in case of real BC break avoiding.

> > A list of functions that allow object on current 5.2:
> > . uksort
> > . uasort
> > . usort
> > . natcasesort
> > . natsort
> 
> Interestingly, this list includes no sort(). Is it intentional? Also, we 
> have a bunch of array functions - wouldn't it make sense that all of 
> them behaved the same way towards objects?

Yep, this was really interesting, see:

$x = new stdclass;
$x->foo = 1;
sort($x);

Warning: sort() expects parameter 1 to be array, object given ...

As other functions that I guess you must be remembered. :)

And yes, I have checked each array function.

-- 
Regards,
Felipe Pena