Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79674 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 91051 invoked from network); 15 Dec 2014 20:49:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Dec 2014 20:49:57 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.214 mail4-2.serversure.net Linux 2.6 Received: from [217.147.176.214] ([217.147.176.214:57688] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/11-18662-3794F845 for ; Mon, 15 Dec 2014 15:49:56 -0500 Received: (qmail 31658 invoked by uid 89); 15 Dec 2014 20:49:52 -0000 Received: by simscan 1.3.1 ppid: 31651, pid: 31654, t: 0.0794s scanners: attach: 1.3.1 clamav: 0.96/m:52/d:10677 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@86.178.188.220) by mail4.serversure.net with ESMTPA; 15 Dec 2014 20:49:52 -0000 Message-ID: <548F4970.9090609@lsces.co.uk> Date: Mon, 15 Dec 2014 20:49:52 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: <4385b3d86ee971aa0f008cc3fcc2e080@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] On the road to PHP 5.7 , or not ? From: lester@lsces.co.uk (Lester Caine) On 15/12/14 20:08, Ferenc Kovacs wrote: > there are two advantages for having 5.7 and having those deprecated > messages in 5.7: > 1, if we introduce the deprecated message in 5.6.x, some people will miss > it (for example debian jessie has 5.6.2) > 2, would allow us to stabilize 5.6 instead of keep adding stuff to it > continuously . And LTS versions can be ring fenced at 5.6 ... with just functional fixes. Perhaps what is needed is a tool which does identify the problems in 5.X code that need to be addressed in order to run clean in PHP7. Rather than encumbering PHP7 with E_STRICT type warning/error code, PHP5.7 would be a test environment to replace that functionality. Once code runs clean then one knows that it can be moved over? Style changes like the 'incorrect ternary '?' associativity' function would be highlighted so that BC problems are not silently changed. A properly documented migration tool rather than a production release as I would not expect to use PHP5.7 in a production environment! -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk