Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82590
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.169 as permitted sender)
Message-ID: <54DDC8BB.9050508@gmail.com>
Date: Fri, 13 Feb 2015 01:49:47 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: wp12173047-156224 wp12173047-156224 <dev@mabe.berlin>, 
 internals <internals@lists.php.net>
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> <1160209871.5291.1423817337421.JavaMail.open-xchange@app07.ox.hosteurope.de>
In-Reply-To: <1160209871.5291.1423817337421.JavaMail.open-xchange@app07.ox.hosteurope.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Remove $this from incompatible context
From: smalyshev@gmail.com (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.
>>
> If every change of a method code is a bc break then you should stop
> coding as bc breaks are evil.

Sorry, I still can't understand this. Who's talking about "every change
is a bc break"? You changed your code so that if was working before but
now it doesn't. It is a bad change. Has nothing to do with the engine.
Has nothing to do with "every change". Has nothing to do with anything
except misguided expectation that if you use some feature in your code
and then change the same code to not have that feature, somehow
(magically?) it is expected to still work. It can't and won't. Either
don't rely on that feature or don't remove it.

> You talked that a method defined as instance method (no static modifier
> defined) will become the same API as if the static modifier were defined

I don't know what you refer to as "same API" but the basic fact - not in
the future, not "will become", not in theory, but in PHP right now -
that the difference is only that static methods can't use $this. All the
rest works the same.

> only because the method doesn't use $this. In my eyes this magically
> changes the API.

Your eyes are wrong, nothing is changing any APIs.

-- 
Stas Malyshev
smalyshev@gmail.com