Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74147
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4NryNu14NVGwEO_OHndkkFr0ubea20c+H5h++QWAiR0X6A@mail.gmail.com>
References: <CAFMT4NqysLiRJH5vye2qbbwwPuAce4e+dRXqkVN2UnwzOw=qvA@mail.gmail.com>
	<536D3C30.9010801@sugarcrm.com>
	<CAFMT4NqMXO4-d6LuN1r2ptfwp3R=CSywPQrVA303JZ7dD=TBKw@mail.gmail.com>
	<CAFMT4NryNu14NVGwEO_OHndkkFr0ubea20c+H5h++QWAiR0X6A@mail.gmail.com>
Date: Tue, 13 May 2014 10:24:58 -0600
Message-ID: <CAFMT4NpU2kg9dbFwoiaxpMW11HC=rK_wEJxPQG3Cbfqwkp_PYQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c303a240d79e04f94a811a
Subject: Re: [PHP-DEV] Anonymous functions inside static methods.
From: morrison.levi@gmail.com (Levi Morrison)

--001a11c303a240d79e04f94a811a
Content-Type: text/plain; charset=UTF-8

> > Another option is to implicitly promote closures inside of static
contexts
> > to be also be static; this is basically what HHVM does.

> PHP does this! That's why you get 'Cannot bind an instance to a static
> closure' if you closure->bindTo() inside a static method, even if
> the closure itself is not keyworded `static`.

I didn't explain that well enough; I meant that it automatically promotes
the
closure to be 'static' in that it uses late static binding.

> The difference between HHVM and PHP is the default class scope of the
> closure. PHP makes the decision that the owning class scope of the
> closure is the compile-time class of the parent method. Why this was
> done I couldn't say.

This is actually the same issue as the one above. Basically the closures
aren't respecting late static binding and I am pretty sure it was just an
oversight, not a conscious decision.

--001a11c303a240d79e04f94a811a--