Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79080 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 9887 invoked from network); 21 Nov 2014 14:16:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2014 14:16:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.178 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.178 mail-wi0-f178.google.com Received: from [209.85.212.178] ([209.85.212.178:62471] helo=mail-wi0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 53/A1-32393-A294F645 for ; Fri, 21 Nov 2014 09:16:11 -0500 Received: by mail-wi0-f178.google.com with SMTP id hi2so8916607wib.17 for ; Fri, 21 Nov 2014 06:16:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=QPbB0pUf/ffq7YsUELwPrgcq+TA/nlivNtVDiMSu0ac=; b=TsE1rld8uEll+bvK8DVWh6FtvCbksoesMiH+mFCH7fKQT9s9c9FrRdCLFgaPfYlnNX 5uwBskver0BcEglEqRyvO9vDSazkXclwSclVHr/7EYhoYjY55eiqDfhd9lfkyrHs48cb xxSD5ylnhzBAcnQLcBJoCLqKix+/xYC84/DpzIz1SGxcZO+Pwz9vVjakken9ZmnNi58Y fLSz6HMN15INYmi5AyGDym5FRcjM1X4FMddmo3k3ny8dn2aLCMvQ1S3xCkOzwx/ikksj E5GhUFh/8kNgrDIF5cy+6MV/jvrpey15tnQXDeOO19J9uv0GkhuK81PqyFR6CIc1i00K ZFRA== X-Received: by 10.194.205.103 with SMTP id lf7mr7808959wjc.134.1416579362729; Fri, 21 Nov 2014 06:16:02 -0800 (PST) Received: from [192.168.0.148] ([62.189.198.114]) by mx.google.com with ESMTPSA id es6sm8237364wjd.29.2014.11.21.06.16.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Nov 2014 06:16:02 -0800 (PST) Message-ID: <546F4910.8040909@gmail.com> Date: Fri, 21 Nov 2014 14:15:44 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: <546C9E22.6090301@fedoraproject.org> <20141119134632.GV2294@phcomp.co.uk> <546CA8C0.1060707@gmail.com> <20141119143329.GX2294@phcomp.co.uk> <1416476628.15061.4.camel@kuechenschabe> <1416502819.15061.38.camel@kuechenschabe> <546F0AA5.30805@lsces.co.uk> <546F2283.5070105@gmail.com> <546F2F5F.6010409@lsces.co.uk> <20141121133615.Horde.P-M9Rdh0CFRidC7Wj6bBaQ6@neo.wg.de> <546F3DB0.2040002@lsces.co.uk> In-Reply-To: <546F3DB0.2040002@lsces.co.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors From: rowan.collins@gmail.com (Rowan Collins) Lester Caine wrote on 21/11/2014 13:27: > No - There have been several threads on deprecating things that are > currently 'hidden' by e_strict. The confusion is created by having two > incompatible styles of coding, and unless one brings the 'non-e_strict' > code in to line with current practices it creates problems when other > actions change the goal posts yet again. So, that would be moving from E_STRICT (safe to hide) to E_DEPRECATED (less safe to hide). At that point, you can deal with the E_DEPRECATED notices *and carry on ignoring E_STRICT*. Unless you can name an example of something which went from E_STRICT to fatal error? If so, that specific case was a violation of process, and should be highlighted. > The confusion is created by having two incompatible styles of coding I asked this before, and you didn't answer: can you name something which, when you fix the E_STRICT notice, makes your code incompatible with something else? Or something which, if you *ignore* an E_STRICT notice, refuses to work? Regards, -- Rowan Collins [IMSoP]