Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78805 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23482 invoked from network); 6 Nov 2014 11:16:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Nov 2014 11:16:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.17.21 mout.gmx.net Received: from [212.227.17.21] ([212.227.17.21:53645] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2B/41-28384-A985B545 for ; Thu, 06 Nov 2014 06:16:43 -0500 Received: from [192.168.0.101] ([91.67.244.80]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MPppG-1XhNEj0KmY-0051Ft; Thu, 06 Nov 2014 12:16:39 +0100 Message-ID: <545B589A.4010606@gmx.de> Date: Thu, 06 Nov 2014 12:16:42 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Lester Caine , internals@lists.php.net References: <3E2593DC-5755-48A6-8802-6F2FB3625778@ajf.me> <04723EAD-4C8E-41C2-BE81-4989882A0C69@ajf.me> <545B26BB.9020406@lsces.co.uk> In-Reply-To: <545B26BB.9020406@lsces.co.uk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:9XQA2QQ1c6yiNhYcwHE/EGq/1t9Hu+aHWqz6OYTPzlHRiZlCLqg GUJJlWjx3OZ/uWDeoMdO0/3zw9MKf+v6DVYsjROXOsQHXYE7ZCq5IioEa+tAntk+0qYz3/N exJKFH9TA5c9imE2+IAUPQ39w7SFXd9AMwFNsA9RGS0l+UShCrGmMZxL3pj2dOJ/7f+XGUk lntl/aCuBWE5IGekDedOQ== X-UI-Out-Filterresults: notjunk:1; Subject: Re: [PHP-DEV] Thresholds of backwards compatibility breaks From: cmbecker69@gmx.de (Christoph Becker) Lester Caine 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 -- Christoph M. Becker