Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79713 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96514 invoked from network); 16 Dec 2014 11:13:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2014 11:13:58 -0000 X-Host-Fingerprint: 212.64.50.33 sd4403221.adsl.online.nl Received: from [212.64.50.33] ([212.64.50.33:9366] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 61/14-07463-CE310945 for ; Tue, 16 Dec 2014 06:13:55 -0500 To: internals@lists.php.net Date: Tue, 16 Dec 2014 12:13:47 +0100 Message-ID: References: <30315309863fc1883f187e2f6777d081@mail.gmail.com> X-Newsreader: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Posted-By: 212.64.50.33 Subject: Re: [PHP-DEV] On the road to PHP 5.7 , or not ? From: phpdev@ehrhardt.nl (Jan Ehrhardt) Patrick Schaaf in php.internals (Mon, 15 Dec 2014 21:36:33 +0100): >Now with PHP 7 promising potential for incompatibilities in a lot more >areas, it would be, to us, a really useful option to have a 5.7 that is >operationally fully compatible with 5.6 with added E_DEPRECATED for things >bound to break. With that we could A) rub the developers' noses in the >relevant deprecation messages for a while, _and_ run one or more rounds of >one-of-the-production -server tests, gathering more deprecation messages >there without fear of user visible effects. I fully agree with you. Not only for migrating our own code a version with deprecation warnings would be helpful. But I think that such a version would also be a big help for migrating frameworks like Drupal ans Wordpress. If you want a move to PHP7 you have to make their migration path smooth. Jan