Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79714 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98023 invoked from network); 16 Dec 2014 11:17:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2014 11:17:12 -0000 Authentication-Results: pb1.pair.com header.from=php@beccati.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=php@beccati.com; spf=pass; 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:55011] helo=mail.beccati.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/64-07463-7B410945 for ; Tue, 16 Dec 2014 06:17:12 -0500 Received: (qmail 1530 invoked from network); 16 Dec 2014 11:17:07 -0000 Received: from home.beccati.com (HELO ?192.168.1.202?) (88.149.176.119) by mail.beccati.com with SMTP; 16 Dec 2014 11:17:07 -0000 Message-ID: <549014A8.70708@beccati.com> Date: Tue, 16 Dec 2014 12:16:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Andrea Faulds , Stanislav Malyshev CC: PHP Internals References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me> <548FFA9A.9080404@gmail.com> <585C233B-7FD9-4A69-B398-B1DB8020298D@ajf.me> In-Reply-To: <585C233B-7FD9-4A69-B398-B1DB8020298D@ajf.me> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC] PHP 5.7 From: php@beccati.com (Matteo Beccati) Hi Andrea, On 16/12/2014 12:10, Andrea Faulds wrote: >> It'd be nice to describe what we have now for 5.7 - i.e. which >> deprecation messages and other warnings are on the agenda? Doesn't have >> to be the exclusive list but at least to give the idea what we're >> talking about. > > At the moment, there’s Levi’s RFC to disallow multiple defaults in switch statements, which adds an E_DEPRECATED notice in 5.7. > > I don’t think there’s anything else. It might be worth adding some sort of warning for Nikita’s Remove alternative PHP tags RFC. Perhaps also for the Integer Semantics RFC, warning that shifts by negative numbers of bits will be disallowed in PHP 7, or for the Fix list() behaviour inconsistency RFC since strings won’t work in list() now. I was initially very much in favour of a 5.7 release, but given the current lack of big BC breaks I'm not so sure. I can even run a dinosaur like Revive on PHP7! If the list of BC breaks grows (e.g. PHP4 constructors -- which I seriously hope doesn't pass -- or other big / evil ones), then I could change my mind once again, but as of now I personally see little gain in a PHP 5.7. That said, I think an RFC is good, but we should run the vote only when we know exactly when PHP7 is going to be, so that everyone can make an informed decision. Doing it now could be premature. Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/