Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:83642 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32164 invoked from network); 24 Feb 2015 08:09:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Feb 2015 08:09:44 -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:43017] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 70/B4-09240-5C13CE45 for ; Tue, 24 Feb 2015 03:09:42 -0500 Received: (qmail 12962 invoked by uid 89); 24 Feb 2015 08:09:38 -0000 Received: by simscan 1.3.1 ppid: 12956, pid: 12959, t: 0.0699s 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.189.147.37) by mail4.serversure.net with ESMTPA; 24 Feb 2015 08:09:38 -0000 Message-ID: <54EC31C2.3010706@lsces.co.uk> Date: Tue, 24 Feb 2015 08:09:38 +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: <54EC262D.9050205@gmail.com> In-Reply-To: <54EC262D.9050205@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Reclassify E_STRICT notices From: lester@lsces.co.uk (Lester Caine) On 24/02/15 07:20, Stanislav Malyshev wrote: >> I would like to propose reclassifying our few existing E_STRICT notices and >> > removing this error category: >> > >> > https://wiki.php.net/rfc/reclassify_e_strict > Could you add some more explanation about why it is a good thing? I.e., > E_STRICT has pretty clear place and hurts no one, why remove it? What we > are trying to accomplish by that? I'm just not seeing how it would be > better without E_STRICT. I don't think that it is necessary to remove the error itself, but some of the coding style elements it currently 'allows' need to be reviewed to see if it is time they were deprecated, allowing some of the new 'strict' elements to be tagged properly in PHP7 ? -- 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