Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82580
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.52 as permitted sender)
Message-ID: <54DD8AA9.3040808@gmail.com>
Date: Thu, 12 Feb 2015 21:24:57 -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: Marc Bennewitz <dev@mabe.berlin>, internals@lists.php.net
References: <CAF+90c8iVRU8-er+05CJqLb7Pg2viR_-zgwf5jmVyfVWx-+-8Q@mail.gmail.com> <54DD1BB1.1090501@gmail.com> <54DD815F.70504@mabe.berlin>
In-Reply-To: <54DD815F.70504@mabe.berlin>
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!

> Such code will break, not in the first place but later on!

Later on when?

> You propose that every instance method not using the variable $this
> internally will be magically a static method and can never ever be

The difference between static method and non-static method is pretty
much this - the former can't use $this.

> changed to use $this without an bc break.

I don't think you use "bc break" in a meaning it is usually used.
Usually, "bc break" means the user code does not change, but the
language or environment changes and code that worked before doesn't work
anymore. That's bad. But you seem to mean that if the user changes the
code to do a different thing than it did before, the code may not be
correct anymore. That's only natural.
-- 
Stas Malyshev
smalyshev@gmail.com