Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71695 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42448 invoked from network); 28 Jan 2014 19:48:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2014 19:48:25 -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.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:40983] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C3/18-01140-78908E25 for ; Tue, 28 Jan 2014 14:48:24 -0500 Received: (qmail 15433 invoked by uid 89); 28 Jan 2014 19:48:21 -0000 Received: by simscan 1.3.1 ppid: 15426, pid: 15430, t: 0.0547s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 28 Jan 2014 19:48:21 -0000 Message-ID: <52E80A0E.7060408@lsces.co.uk> Date: Tue, 28 Jan 2014 19:50:38 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: internals@lists.php.net References: <52E7D67D.1030308@ajf.me> <52E7F55F.7090801@ajf.me> <52E7FCA2.70009@oracle.com> In-Reply-To: <52E7FCA2.70009@oracle.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] some thoughts about php 6 From: lester@lsces.co.uk (Lester Caine) Christopher Jones wrote: > The Python community has similar "discussions", e.g. see the link in: > https://twitter.com/ghrd/status/427879604070526976 The best comment from that is > The solution is clear: build a full compatibility layer, not a conversion tool, into 3.x that makes 2.x code run without change and ABRUPTLY stop development on 2.x. The simple fact that conversion of PY2 code so it will work in PY3 was the problem since there is a MUCH smaller pool of programmers who are capable of the work? It's not unlike PHP4 to 5 since there was little incentive to upgrade systems that were working fine already. Basically as long as PHP6 runs at least the bulk of PHP5.? code then there will not be any major block. The only problem is should it run PHP5.2 code, or only PHP5.6? Little things like only supporting e_strict? -- 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