Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82561
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.171 as permitted sender)
Message-ID: <54DD1E93.1020604@gmail.com>
Date: Thu, 12 Feb 2015 13:43: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: Nikita Popov <nikita.ppv@gmail.com>
CC: PHP internals <internals@lists.php.net>
References: <CAF+90c8iVRU8-er+05CJqLb7Pg2viR_-zgwf5jmVyfVWx-+-8Q@mail.gmail.com>	<54DD1BB1.1090501@gmail.com> <CAF+90c9yxSgSQt6antr=0AbL43sz5PNLcA1SHeY16zmvNEfO9g@mail.gmail.com>
In-Reply-To: <CAF+90c9yxSgSQt6antr=0AbL43sz5PNLcA1SHeY16zmvNEfO9g@mail.gmail.com>
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!

> It was always an E_STRICT error to call a non-static method statically
> (as usual, not counting scoped calls) and since PHP 5.6 it was
> E_DEPRECATED in the most common case. I don't see why we would suddenly
> want to go back on this and make it work without any warnings.

The reason why is simple - it works, it doesn't produce any bad
behavior, it's clear what it does, so why produce warnings that are
essentially useless to the user as they don't warn them about any
potential problem? Unless, of course, I'm missing some potential problem
- please point it out then. But "we've always done it this way" is not
particularly good argument in this case - we did many things one way and
then changed and started doing it a better way.

-- 
Stas Malyshev
smalyshev@gmail.com