Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59012
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F662115.1040000@lsces.co.uk>
References: <4F65A77F.3010001@lsces.co.uk>
	<4F65C87A.70703@thelounge.net>
	<4F6604DC.4040308@lsces.co.uk>
	<CAH-PCH5S1S_Q1=hw9XGJfGwcQqjJRjUqsXKGHHPyAjtfjzywEA@mail.gmail.com>
	<4F662115.1040000@lsces.co.uk>
Date: Sun, 18 Mar 2012 19:00:23 +0100
Message-ID: <CAF+90c9g3ieNgYXFJuxkMg7FHsB2HUGUaWOnS9gKWmLOZSpB5Q@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] PHP5.4 'nannying'
From: nikita.ppv@googlemail.com (Nikita Popov)

On Sun, Mar 18, 2012 at 6:53 PM, Lester Caine <lester@lsces.co.uk> wrote:
> [...] SO my original question still applies, but for different
> reasons ... is there a crib sheet to help eliminate strict code errors in
> legacy code bases?
Uhm, I'm not sure whether I am completely stupid and miss something
obvious: But what exactly is the problem with just reading the error
messages and fixing the errors they report? I mean, you get the reason
for the error and the line which causes it, so what is the problem
with going to that line and fixing that error?

Nikita