Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79078 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 4815 invoked from network); 21 Nov 2014 13:17:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2014 13:17:33 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@beccati.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=php@beccati.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain beccati.com designates 176.9.114.167 as permitted sender) X-PHP-List-Original-Sender: php@beccati.com X-Host-Fingerprint: 176.9.114.167 spritz.beccati.com Received: from [176.9.114.167] ([176.9.114.167:38861] helo=mail.beccati.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DA/D0-32393-B6B3F645 for ; Fri, 21 Nov 2014 08:17:32 -0500 Received: (qmail 27512 invoked from network); 21 Nov 2014 13:17:27 -0000 Received: from home.beccati.com (HELO ?192.168.1.202?) (88.149.176.119) by mail.beccati.com with SMTP; 21 Nov 2014 13:17:27 -0000 Message-ID: <546F3B5C.7040308@beccati.com> Date: Fri, 21 Nov 2014 14:17:16 +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: Jan Schneider , 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> In-Reply-To: <20141121133615.Horde.P-M9Rdh0CFRidC7Wj6bBaQ6@neo.wg.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors From: php@beccati.com (Matteo Beccati) Hi, > I still don't get get what problem this RFC is actually going to solve? > I don't see a problem. Yes, PHP4 constructors are are old and should no > longer be used. But there is no problem still supporting them. Raise an > E_DEPRECATED for those, and be done with it. +1 I can accept BC-breaks if there's a good reason, but this one seems a little weak. For reference 1/3 of the 4500+ php files in the project I work on every day still uses PHP4 constructors. And one third of them is within the bundled PEAR libraries. I'm not saying it is quality code, but it's a dinosaur open source project... I believe that many other historical open source projects are in the same boat. All the (unpaid) time that the team(s) would need to waste on this could be better spent elsewhere. Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/