Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74119
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4NqMXO4-d6LuN1r2ptfwp3R=CSywPQrVA303JZ7dD=TBKw@mail.gmail.com>
References: <CAFMT4NqysLiRJH5vye2qbbwwPuAce4e+dRXqkVN2UnwzOw=qvA@mail.gmail.com>
	<536D3C30.9010801@sugarcrm.com>
	<CAFMT4NqMXO4-d6LuN1r2ptfwp3R=CSywPQrVA303JZ7dD=TBKw@mail.gmail.com>
Date: Sat, 10 May 2014 21:18:21 -0600
Message-ID: <CAFMT4NryNu14NVGwEO_OHndkkFr0ubea20c+H5h++QWAiR0X6A@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bd74ce06c039904f91748d4
Subject: Re: [PHP-DEV] Anonymous functions inside static methods.
From: morrison.levi@gmail.com (Levi Morrison)

--047d7bd74ce06c039904f91748d4
Content-Type: text/plain; charset=UTF-8

On Sat, May 10, 2014 at 9:12 PM, Levi Morrison <morrison.levi@gmail.com>wrote:
>
> > I think Bar::bar() should definitely return 'Bar' (currently returns
> > 'Foo') but what about the Bar::Baz() call?
>
> I kinda agree, but that ship has sailed and it would be a BC break.
>

Yes... but we fix bugs all the time that are technically BC breaks. Do you
really think we shouldn't fix this?

I note in your 3v4l that HHVM does not follow the same rules.
>

I think HHVM gets the Bar::bar() case correct and we should fix it.

I'm not sure if I agree with HHVM's outcome on Bar::baz(). To me the
closure is non-static which means it won't invoke late static binding. This
is something I'd like to discuss; what do you guys think about that?
Another option is to implicitly promote closures inside of static contexts
to be also be static; this is basically what HHVM does.

--047d7bd74ce06c039904f91748d4--