Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82734
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.179 as permitted sender)
User-Agent: K-9 Mail for Android
In-Reply-To: <54DFAA20.4000900@mabe.berlin>
References: <CAF+90c8iVRU8-er+05CJqLb7Pg2viR_-zgwf5jmVyfVWx-+-8Q@mail.gmail.com> <54DD1BB1.1090501@gmail.com> <54DD815F.70504@mabe.berlin> <54DD8AA9.3040808@gmail.com> <752856272.5008.1423809953291.JavaMail.open-xchange@app07.ox.hosteurope.de> <54DDAC30.7090206@gmail.com> <54DFAA20.4000900@mabe.berlin>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8
Date: Sun, 15 Feb 2015 18:09:54 +0000
To: internals <internals@lists.php.net>
Message-ID: <0C346B4A-94E7-4865-9698-044F21FDBC5F@gmail.com>
Subject: Re: [PHP-DEV] Remove $this from incompatible context
From: rowan.collins@gmail.com (Rowan Collins)

On 14 February 2015 20:03:44 GMT, Marc Bennewitz <dev@mabe.berlin> wrote:
>Hi
>Am 13.02.2015 um 08:48 schrieb Stanislav Malyshev:
>> Hi!
>>
>>> there should be no bc break as the API doesn't change and the method
>>> produces the exact same result as before.
>> Sorry, this makes no sense to me. You claim that if you changed the
>> method code to do different thing it should continue working as if
>you
>> didn't change it? Why? I just don't get it.
>>
>>> It's not a good thing to magically change the method API in base of
>a
>>> method body that's not port of the API.
>> "magically change the method API"? What are you talking about? You
>> changed the code, not magic.
>>
>Sorry it wasn't clear. I hope I will now:
>
>The static modifier for methods is part of the method signature and 
>method body isn't.
>(That's way interfaces doesn't describe method bodies but signatures)
>
>The static modifier defines a method as static and therefore defines
>the 
>method is callable using "::".

More specifically, it defines that the method is *only* callable statically. There is currently no opposite keyword to say that a method can only be called non-statically, but the absence of a modifier has up until now meant that either call type is possible. An interface cannot currently forbid static calls, only the use of $this.

Our choice is between keeping that ambiguity, and introducing a new rule that any method not marked static must never be called statically (with provisos for technically non-static parent:: etc).

Regards,
-- 
Rowan Collins
[IMSoP]