Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91507 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85450 invoked from network); 5 Mar 2016 09:33:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Mar 2016 09:33:39 -0000 X-Host-Fingerprint: 80.177.120.119 marston-home.demon.co.uk Received: from [80.177.120.119] ([80.177.120.119:16541] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8B/90-08669-1F7AAD65 for ; Sat, 05 Mar 2016 04:33:37 -0500 Message-ID: <8B.90.08669.1F7AAD65@pb1.pair.com> To: internals@lists.php.net References: In-Reply-To: Date: Sat, 5 Mar 2016 09:33:21 -0000 Lines: 2 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 80.177.120.119 Subject: Re: [RFC] Deprecations for PHP 7.1 From: TonyMarston@hotmail.com ("Tony Marston") "Stephen Coakley" wrote in message news:DB.F0.25279.8C0D9D65@pb1.pair.com... > >On 02/18/2016 06:41 AM, Nikita Popov wrote: >> Hi internals! >> >> I've created a bulk-deprecation RFC for PHP 7.1: >> https://wiki.php.net/rfc/deprecations_php_7_1 >> >> I'm using this RFC to collect various deprecations targeting PHP 7.1, as >> having individual RFCs for these is too much management overhead. Each >> deprecated feature will get its own vote, of course. >> >> This RFC is incomplete -- I'm posting it now so people can suggest other >> things that should be deprecated. I expect it to grow over time and don't >> plan to vote on it in the immediate future. >> >> Thanks, >> Nikita >> > >My stance on deprecations: > > > It seems that perfection is attained not when there is nothing more > > to add, but when there is nothing more to remove. > > - Antoine de Saint Exupéry > >I'd say any function that provides duplicate functionality, or encourages >bad practice, should be deprecated. Keeping the standard library clean and >focused is ideal. But who decides what is "bad" practice and what is not? It is impossible for ANY language to prevent a bad programmer from writing bad code, so the only way to prevent bad code 100% would be to have a language that did nothing at all. Deprecating something just because you don't like is NOT a good enough reason. -- Tony Marston