Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85010 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33203 invoked from network); 16 Mar 2015 09:07:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2015 09:07:12 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:47345] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C0/D5-00492-D3D96055 for ; Mon, 16 Mar 2015 04:07:10 -0500 Received: (qmail 7869 invoked by uid 89); 16 Mar 2015 09:07:06 -0000 Received: by simscan 1.3.1 ppid: 7863, pid: 7866, t: 0.0846s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.178.189.108) by mail4.serversure.net with ESMTPA; 16 Mar 2015 09:07:06 -0000 Message-ID: <55069D3A.9020806@lsces.co.uk> Date: Mon, 16 Mar 2015 09:07:06 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: internals@lists.php.net References: <54FF8CED.5030701@gmail.com> <54FFC96D.6090004@gmail.com> <1579682575.9673.1426064704052.JavaMail.open-xchange@app06.ox.hosteurope.de> <55000A88.1030909@lsces.co.uk> <55060A95.1020901@gmail.com> <550698E2.8060802@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV][RFC][DISCUSSION] Strict Argument Count From: lester@lsces.co.uk (Lester Caine) On 16/03/15 08:51, Marco Pivetta wrote: > On 16 March 2015 at 08:48, Lester Caine wrote: > >> > The problem here is simply that just what error's are enabled and >> > disabled is getting more difficult to decide? If when moving from a >> > currently clean environment which has every error displayed and only >> > shows something when any problem arises then moving to a new major >> > version do we have to switch everything off again since all types of >> > errors will now be thrown by the previously clean code. >> > >> > This is the problem currently in the PHP5.2->5.4 dilema. Yes you can >> > switch errors off and the code runs, but then how do you address the >> > problems. Added to which something hidden by E_DEPECATED in 5.3 is now >> > no longer available in 5.4, but the code is still 5.2. >> > > We are talking about codebases with strict no-notice and no-warning > policies. > > Disabling error reporting is not going to cut it here, as we all test our > stuff with E_ALL. Exactly my point! But getting millions of lines of existing code TO that state requires a little time, especially when the goal posts keep moving. Which is why I've set the goal posts at 5.4 at the moment. The 5.2/3 stuff is finally starting to get there, but I can't switch off the 5.2 services yet :( Then I need the PHP5.4 base to run on the PHP7 without a problem ... just how much time that will take is unknown as yet, so being able to switch off errors that are non-urgent to fix is a useful tool, otherwise why have different types of error at all? But this is why PHP5.7 might have been a sensible stepping stone in the battle to GET a clean code base. -- 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