Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:47420
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.224 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=cDWAdpqcyqN/E9F6XUjlf3kKj9dIcPPTaMWizJb16Mtaob3xw5zH3S8iVDIr/ynXJH
         bKu9v8k5fyN5lweLfoFWkeTfRPu8UYwUjFvCkspGwt29j+8Db6q4w5Rcy9kGN7X/ES5R
         XuFAkINLrIOHFkLbTInJUy0oOaZFWl2y/eJAk=
MIME-Version: 1.0
Sender: ekneuss@gmail.com
In-Reply-To: <4BA25919.8090805@easyflirt.com>
References: <4BA0DF61.1010907@easyflirt.com> <4BA0E39C.7020600@gmail.com>
	 <4BA0E9E8.8000404@easyflirt.com>
	 <e666c3891003171419t35b0df06v6c1d502c270154de@mail.gmail.com>
	 <4BA1DB19.1080608@easyflirt.com>
	 <660eb66f1003180224g5662ba1dtb123c3ee88a3a3e5@mail.gmail.com>
	 <4BA25919.8090805@easyflirt.com>
Date: Fri, 19 Mar 2010 03:56:19 +0100
Message-ID: <e666c3891003181956j7c64948cq5ca791be21ab1dbc@mail.gmail.com>
To: "mathieu.suen" <mathieu.suen@easyflirt.com>
Cc: Peter Lind <peter.e.lind@gmail.com>, internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Assign array with __get
From: webmaster@colder.ch (Etienne Kneuss)

On Thu, Mar 18, 2010 at 5:47 PM, mathieu.suen
<mathieu.suen@easyflirt.com> wrote:
> Peter Lind wrote:
>>
>> On the contrary, it's quite obvious what's going on. In both examples
>> __get() returns an array as PHP would normally do it (i.e. NOT by
>> reference) which means that if you try to modify that you'll end up
>> modifying nothing much. However, in your second example, the point at
>> which you call __get() indirectly comes before the assign to the zork
>> array - hence, the $this->zork['blah'] =3D 'blah'; no longer indirectly
>> calls __get as object::$zork now exists.
>>
>> =A0In other words, this is down to you confusing passing a variable by
>> reference and passing it by value: PHP normally passes arrays by
>> value, so when __get() returns an array, you're working on a copy of
>> the array you returned. As someone noted earlier, you can easily
>> change the behaviour of __get to return variables by reference, should
>> you want to. However, I personally wouldn't want this to be default
>> behaviour as that would make debugging apps much more annoying -
>> things should be consistent, even if consistency at times confuse
>> people.
>>
>> Regards
>> Peter
>>
>>
>
> The sementic of
>
> $this->zork
>
> Should be the same as
>
> $this->__get('zork')
>

$this->zork is only the same as $this->__get("zork") if zork is
undefined, this is perfectly normal and expected.

> So in that respect it is not consistent.
>
> But anywhere I don't care if =A0it change or not.
>
> Look at Scheme, Lisp and Smalltalk language.
> This is what I call consistent language.
>
>
> -- Mathieu Suen
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



--=20
Etienne Kneuss
http://www.colder.ch