Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78813
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
Message-ID: <545B66AB.2000109@lsces.co.uk>
Date: Thu, 06 Nov 2014 12:16:43 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "internals@lists.php.net >> PHP internals" <internals@lists.php.net>
References: <CABRjmp-oqEVtX-igQWsr-JkFmitqxn4YsyJ=mnzyHCN9Kj7akA@mail.gmail.com> <CAH-PCH62GAecxC00aHgzgskG8zk58z1LBE1uBv81xtj6hRiy5w@mail.gmail.com> <3E2593DC-5755-48A6-8802-6F2FB3625778@ajf.me> <CAEZPtU5bdrgX3yfNZhPsWqrU6d5fw=vX78-iW=gx1jUJoeF8YA@mail.gmail.com> <04723EAD-4C8E-41C2-BE81-4989882A0C69@ajf.me> <545B26BB.9020406@lsces.co.uk> <545B589A.4010606@gmx.de>
In-Reply-To: <545B589A.4010606@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Thresholds of backwards compatibility breaks
From: lester@lsces.co.uk (Lester Caine)

On 06/11/14 11:16, Christoph Becker wrote:
>> Yes it is only a number, but a lot more problematic changes WERE pushed
>> > through across those three versions which would have been much safer
>> > handled by removing e_strict from PHP5.4 rather than trying to live with
>> > both versions of PHP.
> I don't see a problem with regard to E_STRICT.  If your code is not yet
> strict compliant, simply turn it off for error_reporting:
> 
>   error_reporting = E_ALL & ~E_STRICT

I get tired say this !!!

The problem is trying to maintain TWO totally incompatible code bases
side by side. It is all to easy to have a wrong setting, or pick up a
'e_strict' version library with a not yet fixed set of code!
If many of the libraries I work with had NOT been updated there would be
less of a problem, but the ONLY way to prevent white screen sites is to
get rid of all of the old code ... which is still unfortunately work in
progress ...

Keeping the non e-strict code on a PHP5.2 powered server and only using
e_strict compliant on the PHP5.4, we maintain stable operation, but
ISP's are upgrading shared hosting and that is where ring fencing the
legacy code is time consuming and detracting from getting code cleaned up.

And switching off error reporting only adds to the problems recovering
sites which have gone down. I know people seem to think that this is not
acceptable on production sites, but my code had always run clean and a
visible error can be picked up and fixed while checking through a large
number of log files across many services to see if there are problems is
not something I want to spend my days doing!

Screwing up the code and then hiding the results is NOT maintaining BC!

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk