Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41929
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.157 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=qPqxN5FFmhobM1Si1HDtwA6i+Eh7ZogggcyYFoAcyOg9vdl0mCaVAw6NRGKT1DiRu2
         nOhFeFR/DcCsE1W5XiOrN4prCM+biVk7D0ZT4ex48KsMSRdUAUjVjfj+kdK80uzoE2oc
         LLxEY5vGZ35qQ20sNMslea2cByuT1TRoi3XDE=
Message-ID: <2dedb8a0811151048pda86b4dje44ec5ceb1b7740a@mail.gmail.com>
Date: Sat, 15 Nov 2008 19:48:09 +0100
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "Stanislav Malyshev" <stas@zend.com>, "Felipe Pena" <felipensp@gmail.com>, 
	"Geoffrey Sneddon" <foolistbar@googlemail.com>, 
	"PHP Internals" <internals@lists.php.net>
In-Reply-To: <4A1C7FFD-F85F-4D61-BEDA-7C0D31485C35@pooteeweet.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4900DB81.4000805@zend.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>
	 <F88778E6-1A35-499F-82C9-7EE7D7D3FBA0@pooteeweet.org>
	 <491C6FAF.104@zend.com>
	 <4A1C7FFD-F85F-4D61-BEDA-7C0D31485C35@pooteeweet.org>
Subject: Re: [PHP-DEV] array_key_exists BC break
From: kalle.php@gmail.com ("Kalle Sommer Nielsen")

2008/11/15 Lukas Kahwe Smith <mls@pooteeweet.org>:
>
> On 13.11.2008, at 19:19, Stanislav Malyshev wrote:
>
>> Hi!
>>
>>> Can anyone write up a summary of the situation and the options we have?
>>
>> Sure. A number of array functions in 5.2 accept arrays, but use HASH_OF to
>> extract array value, which means they automatically accept objects if the
>> object has working get_properties handler. In 5.3, such function use new API
>> with 'a' parameter, which accepts only arrays proper.
>> The proposal is to have some new parameter - say 'a%' - which would call
>> HASH_OF on objects where it makes sense. The definition of "makes sense" is
>> not clear yet, since, for example, sort() on some objects may make sense -
>> if the object's get_properties returns real storage - or may not, if that
>> handler returns the mere copy of the real data. We might use some interface
>> as a marker - like ArrayAccess - though I'm not sure if it will work in all
>> circumstances.
>
> So what if we for now stick with the BC fix?
> However maybe for PHP 6.0 we should make a real effort to figure out how
> objects are supposed to be handled in our PHP type juggeling world.
>

I think we should fix it, if theres BC its most likely people will
draw away from using it, especially people writing cross version
applications if they have to "hack" their way to use this feature. I
like Stas' suggestion for changing the parameter parsing api to
support it like that.



-- 
Kalle Sommer Nielsen