Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75299 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2735 invoked from network); 7 Jul 2014 12:12:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jul 2014 12:12:08 -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:39374] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 58/51-21356-59E8AB35 for ; Mon, 07 Jul 2014 08:12:07 -0400 Received: (qmail 24738 invoked by uid 89); 7 Jul 2014 12:12:03 -0000 Received: by simscan 1.3.1 ppid: 24729, pid: 24735, t: 0.0718s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO ?10.0.0.8?) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 7 Jul 2014 12:12:03 -0000 Message-ID: <53BA8E93.8060708@lsces.co.uk> Date: Mon, 07 Jul 2014 13:12:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: internals@lists.php.net References: <61EEC54E-7B8D-433E-A391-75F8D6A41E79@ajf.me> <650742796f119ed972a688a58e02242b@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Name of Next Release of PHP From: lester@lsces.co.uk (Lester Caine) On 07/07/14 12:31, Pierre Joye wrote: > I seriously hope that you take 2015 as pure example here. As I see no > remote chance to be ready next year. PHPNG is a huge stack of > undocumented perf patches far from being ready, APIs &code cleanup did > not even begin, and the existing APIs are even more ugly. This is not > going to be a small task, besides other things that we may like to > have in the next major version. A 2 years development period sounds > much more realistic to me. If that is a realistic roadmap, then what also needs to be added is just what happens with the PHP5 in the meantime. From my own view, some elements of 'PHP6' are still overdue, but if it will be yet another couple of years then should we be looking at an interim solution for 'bigint' and unicode? While reworking the entire code base to give a performance improvement is a perfectly sensible long term plan it sidesteps the 'problems' that PHPNext should ideally address. There are perhaps two conflicting paths here? -- 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