Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38011 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15923 invoked from network); 30 May 2008 10:49:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 May 2008 10:49:05 -0000 Authentication-Results: pb1.pair.com header.from=steph@zend.com; sender-id=softfail Authentication-Results: pb1.pair.com smtp.mail=steph@zend.com; spf=softfail; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain zend.com does not designate 64.99.136.129 as permitted sender) X-PHP-List-Original-Sender: steph@zend.com X-Host-Fingerprint: 64.99.136.129 smtprelay-virgin0129.hostedemail.com Linux 2.5 (sometimes 2.4) (4) Received: from [64.99.136.129] ([64.99.136.129:56790] helo=smtprelay-virgin.hostedemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EF/67-03918-0ABDF384 for ; Fri, 30 May 2008 06:49:05 -0400 Received: from filter.hostedemail.com (ff-bigip1 [10.5.19.254]) by smtprelay04.hostedemail.com (Postfix) with SMTP id 08964B13ED for ; Fri, 30 May 2008 10:49:02 +0000 (UTC) X-SpamScore: 1 Received: from foxbox (host81-155-113-213.range81-155.btcentralplus.com [81.155.113.213]) (Authenticated sender: steph.fox) by omf10.hostedemail.com (Postfix) with ESMTP for ; Fri, 30 May 2008 10:49:01 +0000 (UTC) Message-ID: <00cf01c8c242$f1a6ce10$4401a8c0@foxbox> Reply-To: "Steph Fox" To: "internals" Date: Fri, 30 May 2008 11:50:13 +0100 Organization: Zend Technologies MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-session-marker: 73746570682E666F78 X-Spam-Summary: 2,0,0,b4d817793352d002,0ea2c16140c65924,steph@zend.com,,RULES_HIT:152:355:379:539:540:541:542:543:567:945:973:988:989:1155:1156:1260:1277:1311:1313:1314:1345:1437:1515:1516:1518:1534:1541:1587:1593:1594:1676:1711:1730:1747:1766:1792:2073:2075:2078:2379:2393:2559:2562:3353:3865:3866:3867:3868:3869:3870:3871:3872:3873:3874:4250:4362:5007:6119:6261:7875,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:none,DNSBL:none Subject: New flame From: steph@zend.com ("Steph Fox") Hi all, I'd like to set the world on fire before disappearing off for the rest of the day, so bear with me :) PHP 5.3 appears (to me at least) ready for release, give or take a bit of ironing. The only problem is the one of other-version compatibility, which really is a PHP 6 issue. We can't (well we can but it doesn't work well) future-proof our code with any certainty that we're doing so correctly. That goes for both internal code (where it matters slightly less in that it doesn't affect users) and userland code (where it matters a lot). If you adapt userland code in PHP 5.3 to run under PHP 6, you lose back compatibility prior to PHP 5.2.1. If this changes in PHP 6 after PHP 5.3 is released, ie PHP 6 is made more BC-friendly at too late a stage, there are likely to be an awful lot of users complaining about their wasted time re-writing code when they had to make a choice between FC and BC. I therefore see tackling the BC issues in PHP 6 as a priority at this point for this reason. I know a handful of developers (Tony, Scott, Andrei to name the main movers at present) are ready to start working on HEAD again once its direction is settled, and I'm concerned it's all going to come too late to prevent a minor crisis of confidence. So can we focus on 6 for a bit please? Like, make it Unicode-only and iron out the BC issues arising from that as far as is possible? Thanks, - Steph