Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55739
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <op.v2zwb3u2idpuyk@cataphract-old.dulce.lo.geleia.net>
References: <4E5B24DD.10903@sugarcrm.com>
	<op.v0yn2z06idpuyk@damnation>
	<4E671355.5060908@sugarcrm.com>
	<CAH-PCH4JaCrbuQzL+c5M6vYjfNEJXAUktLxmc7w5pfuLqdYiSQ@mail.gmail.com>
	<op.v2zwb3u2idpuyk@cataphract-old.dulce.lo.geleia.net>
Date: Fri, 7 Oct 2011 21:32:24 +0200
Message-ID: <CAH-PCH7QtBSxLix6J5LV=EMiuG7u7STx-3a-mp56ib6a0M+K0A@mail.gmail.com>
To: Gustavo Lopes <glopes@nebm.ist.utl.pt>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] 5.4 beta
From: tyra3l@gmail.com (Ferenc Kovacs)

'

On Fri, Oct 7, 2011 at 8:58 PM, Gustavo Lopes <glopes@nebm.ist.utl.pt> wrot=
e:
> On Fri, 07 Oct 2011 18:31:42 +0100, Ferenc Kovacs <tyra3l@gmail.com> wrot=
e:
>
>> do we have a wiki/documentation about what exactly ended up in 5.4
>> from the Closure improvements? (Rebind)
>>
>> https://wiki.php.net/rfc/closures/object-extension#privateprotected_memb=
ers_scope
>> is really hard to read, as it contains all of the suggested ideas and
>> possible solutions, etc.
>> if not, maybe someone with the required knowledge =C2=A0could start work=
ing
>> on adding the documentation?
>>
>
> I don't think so, but if I had to summarize the innovations in 5.4, this
> would be it:
>
> - Closures can now have an associated scope
> - Closures can now have a bound object
> - Closures can now be either static or non-static
>
> - Closures defined in a place with an active scope are scoped accordingly
> - Closures defined inside an instance method (or bound closure) have a bo=
und
> object (namely $this)
> - Closures are static if defined within a static method or with the stati=
c
> keyword (static function() { ... })
>
> static =3D> !bound
> (but it's false that !static =3D> bound)
> bound =3D> scoped
> !static && scoped =3D> bound
> (i.e., if !static, scoped <=3D> bound)
>
> The bound instance and the scoped can be freely changed with Closure::bin=
d
> and $closure->bindTo, subject to these constraints.

"- Closures can now have an associated scope"
as it is https://wiki.php.net/rfc/closures/object-extension#privateprotecte=
d_members_scope
?
at first I thought that scope means Variable scope, but I think I get
it now: it means that when the Closure calls/access something through
$this, it will be handled as it was called/accessed from the given
class(scope).
and this also explains why we had to add the third param for Closure::bind.
the bound param defines what is the $this pointing to, and the scope
means that from what scope would be used for accessing the $this.
having a static Closure means that it won't have the $this, but it can
still have a scope (so it can interact with other static methods).

thanks, I think I managed to wrap my head around that!

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu