Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61767
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <500F7B9F.4070103@garfieldtech.com>
References: <CAF+90c-eG_+7ZpGzu-ownYnTDUvVJwHgCH=xOvnOa9sAYKNHjA@mail.gmail.com>
 <1342050547.1456.33.camel@guybrush> <CAAyV7nGg=LwgLADXRP5b+LE79qJTRjf63J-3CgFyWmb6aJAieA@mail.gmail.com>
 <CAESVnVpF1fQv0E2fzsOP1vUX5+myVn00a47ceZeNpKuuCS+XSA@mail.gmail.com>
 <D8.3A.46517.587EEFF4@pb1.pair.com> <4FFF6C9C.2080802@gmail.com>
 <36.A6.17670.8E820005@pb1.pair.com> <CAMUwpuQgtJqRxv_6rT4JDCXnBn+_ORAFRGQG9sa2D=Yjv-jnSw@mail.gmail.com>
 <50005B38.3090507@sugarcrm.com> <5000BCD2.2040007@garfieldtech.com>
 <5000BEE9.3070006@sugarcrm.com> <CAMUwpuQFiEOatWxjbVLawN8+h=HYUq=5JGDi7NSZc3f2A_mVMw@mail.gmail.com>
 <500F7B9F.4070103@garfieldtech.com>
Date: Wed, 25 Jul 2012 17:16:40 +0200
Message-ID: <CAMUwpuS+QULG3jGgKXVLdkxJ3pJOB8+=RVAPfxC3SK+aAa4QVw@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Internal iteration API
From: jpauli@php.net (jpauli)

On Wed, Jul 25, 2012 at 6:52 AM, Larry Garfield <larry@garfieldtech.com> wrote:
> On 07/24/2012 03:52 AM, jpauli wrote:
>>
>> On Sat, Jul 14, 2012 at 2:35 AM, Stas Malyshev <smalyshev@sugarcrm.com>
>> wrote:
>>>
>>> Hi!
>>>
>>>> So, I've not been inside the engine so in practice this may make no
>>>> sense at all, but what about looking at it the other way around?  Vis,
>>>> instead of making objects more and more like arrays, make arrays an
>>>> object that happens to implement ArrayAccess, Iterator, and whatever
>>>
>>> That'd be very nice idea if we were implementing new PHP. I think the
>>> fact that arrays are not objects in PHP is a source of many problems.
>>> However, right now it probably won't be possible to do it without
>>> breaking BC in many places dealing with array copy/assignment/passing
>>> semantics.
>>
>> I'd then say : let's keep that idea somewhere to implement it in a new
>> major PHP version.
>> Anyway, there will come a time where we will be developing for PHP6
>> (or PHP next Major if you prefer), and I think we should use
>> this gap to break BC and add new cool ideas like this one, we seem all
>> to agree with.
>>
>> Julien.P
>
>
> Agreed.  We survived Objects becoming, er, Objects in PHP 5.0. Arrays
> changing would be a major version change, but if the benefits are enough, we
> could survive that, too.

+1 great notice.
We had a huge step between PHP4 and PHP5. It's done now (hence it
wasn't that easy to achieve).
So it wont be frightening to see another gap between PHP5 and
PHP-NEXT-MAJOR , especially if it's lower than 4-to-5 was.

Julien.P