Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82605
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.53 as permitted sender)
Message-ID: <54DDE240.80507@gmail.com>
Date: Fri, 13 Feb 2015 11:38:40 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: PHP internals list <internals@lists.php.net>
References: <CAF+90c8iVRU8-er+05CJqLb7Pg2viR_-zgwf5jmVyfVWx-+-8Q@mail.gmail.com>	<006b01d046d4$0674e6c0$135eb440$@tekwire.net>	<54DCDA71.8070201@gmail.com> <CAKOpQSzXs_6QG5wwRoBKWOd-UxF1zf=YiQ4OSONJCar=b1V2SA@mail.gmail.com>
In-Reply-To: <CAKOpQSzXs_6QG5wwRoBKWOd-UxF1zf=YiQ4OSONJCar=b1V2SA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Remove $this from incompatible context
From: rowan.collins@gmail.com (Rowan Collins)

Kris Craig wrote on 12/02/2015 21:45:
> Since it's very common for environments to display E_WARNING but not 
> E_NOTICE, some devs-- particularly those who are less experienced in 
> PHP-- can end up wasting a lot of time trying to chase down the 
> behavior because they're not seeing any errors.

If people have turned off E_NOTICE, there is presumably something in 
that level that they don't want to see; giving them that choice is the 
whole point of having multiple reporting levels in the first place. 
Without a clear definition of what should be in each level, there's a 
risk of inflation setting in, with advocates of each message saying why 
people should see it even if they have E_NOTICE turned off.

The alternative, which I've tried to picture before, is a more 
customisable system based on types of message rather than severity - so 
that a user who has a lot of $foo[$new_key][$new_sub_key] = $value in 
their code can suppress E_ACCESSING_NONEXISTENT_ARRAY_KEY, and a user 
who has a lot of $foo[unquote_key] can suppress 
E_UNDECLARED_CONSTANT_USED_AS_STRING (obviously with better names than 
that!). That way important messages which you definitely want to fix 
don't get drowned in the noise of things which you know you should get 
around to fixing one day but are working as designed right now.

Regards,
-- 
Rowan Collins
[IMSoP]