Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79075 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95159 invoked from network); 21 Nov 2014 11:31:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2014 11:31:41 -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.172 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.172 mail-wi0-f172.google.com Received: from [209.85.212.172] ([209.85.212.172:60898] helo=mail-wi0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F9/80-25456-D922F645 for ; Fri, 21 Nov 2014 06:31:41 -0500 Received: by mail-wi0-f172.google.com with SMTP id n3so11690873wiv.17 for ; Fri, 21 Nov 2014 03:31:37 -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=7ey8svGZsTWF01ZTiU3qbi5B1G7yfemcJaNFHh53zI4=; b=py5FlCcRhTv/sQAC5M5y+I38BZfjNleQIQMncvUmO+YIv61xMqpzWzYgVuHNZw3lKc lPVphZG48sv5BddkVczJiHdBpGgbM6wKa8b9nSaR2d5f2Q4ugp1E/RMkwG0he/tw9AZ8 EFHSU6nITQ68Oqw8gyIGhc9FqjJHcPXSH/IwCrXBTz56dacmYx33bQ+ohoLRTN9c5Ic8 wum0IGwEFWhnVEJ022ZhjfDp5QRqhsUf1aBLMa8p+Oy7XWa8zTZl63onXh0lYRB9XbiJ Q8Lm06YP2uD27wYo8ULdWlCNBMeoijguMXzd5qATarfxMWNkpsfeJgZqOT7FatSqm0OJ pqtQ== X-Received: by 10.194.156.201 with SMTP id wg9mr6480497wjb.59.1416569495855; Fri, 21 Nov 2014 03:31:35 -0800 (PST) Received: from [192.168.0.148] ([62.189.198.114]) by mx.google.com with ESMTPSA id p7sm7649291wjo.38.2014.11.21.03.31.34 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Nov 2014 03:31:35 -0800 (PST) Message-ID: <546F2283.5070105@gmail.com> Date: Fri, 21 Nov 2014 11:31:15 +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> In-Reply-To: <546F0AA5.30805@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 09:49: > I know I sound like a broken record, but this is EXACTLY the same > problem as e_strict! It is all very well saying old code can still run > if you hide the the warnings and ERRORS, but you have to spend the time > fixing each and every warning simply to ensure that it will work on the > next release ... hiding things does not work. > > And I still run my own version of PEAR to get around the e_strict problems! To reply with a broken record of my own: E_STRICT does not indicate code that will break in a future version. Hiding E_STRICT notices will have absolutely no detrimental effect on your code, now or in the future. It is up to you if you want to improve the code by following the hints, or ignore them because the code works fine. So, no this is not at all similar to the "problem" of E_STRICT, because that problem is not real. Regards, -- Rowan Collins [IMSoP]