Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30984 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65936 invoked by uid 1010); 16 Jul 2007 15:54:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 65900 invoked from network); 16 Jul 2007 15:54:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jul 2007 15:54:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=jani.taskinen@sci.fi; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=jani.taskinen@sci.fi; sender-id=unknown Received-SPF: error (pb1.pair.com: domain sci.fi from 63.208.196.171 cause and error) X-PHP-List-Original-Sender: jani.taskinen@sci.fi X-Host-Fingerprint: 63.208.196.171 outbound.mailhop.org FreeBSD 4.6-4.9 Received: from [63.208.196.171] ([63.208.196.171:4067] helo=outbound.mailhop.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 40/7E-62403-5FD8B964 for ; Mon, 16 Jul 2007 11:25:43 -0400 Received: from [81.22.163.71] (helo=[10.6.109.91]) by outbound.mailhop.org with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.63) (envelope-from ) id 1IASS6-000FE2-4H; Mon, 16 Jul 2007 11:25:34 -0400 X-MHO-User: U2FsdGVkX1+6+97VqU+Ii9K9cBEp+3tAfL/ote1fNg0= X-MHO-User: U2FsdGVkX1+5gReZLXcst+BT2p+vqCNhwQZbpLfMaY0= X-MHO-User: U2FsdGVkX1+oSesicKJznadkLKLz/FDqxkt2TZ0U9Nw= X-MHO-User: U2FsdGVkX19pS8vISPYEqlKH2HFVtpf0MZrXiSUH0aw= X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 81.22.163.71 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1839COIiARmM9A6aqHe3y375uUPcxL1fGw= Reply-To: jani.taskinen@iki.fi To: Antony Dovgal Cc: Lukas Kahwe Smith , Andi Gutmans , Ilia Alshanetsky , internals@lists.php.net In-Reply-To: <469B8C73.8020908@zend.com> References: <698DE66518E7CA45812BD18E807866CE648191@us-ex1.zend.net> <54C4340A-D9EA-4B5A-B39C-B55B29B1B3BC@prohost.org> <698DE66518E7CA45812BD18E807866CE648193@us-ex1.zend.net> <469B7FB1.1070507@pooteeweet.org> <469B8C73.8020908@zend.com> Content-Type: text/plain Date: Mon, 16 Jul 2007 18:25:31 +0300 Message-ID: <1184599531.3352.22.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-2.fc6) Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] POSIX regex From: jani.taskinen@sci.fi (Jani Taskinen) Thank you Lucas and Antony. Could not agree more.. On Mon, 2007-07-16 at 19:19 +0400, Antony Dovgal wrote: > Thank you Lukas for expressing exactly my thoughts on this. > > On 16.07.2007 18:24, Lukas Kahwe Smith wrote: > > Andi Gutmans wrote: > >> Even in PHP 6 I am not sure it's a good idea. There are a huge amount of > >> apps that use them and it'll be very hard for people to upgrade. > >> Anyway, let's do some more research on that once we get closer to PHP 6 > >> and see what the migration path looks like. We'll have to check with a > >> few popular apps + google code search :) > >> No need to decide on that right now without having more info. > > > > I disagree with this approach. The thing is that we need to get a clear > > message out ASAP. This all ties into topics like if we will have a > > unicode off/on switch or not. Delaying these decisions will hurt our > > userbase. We need to prepare them early. > > > > IMHO we should use PHP6 as the clean up release. Drop unicode on/off > > switch, accept that the bulk of all code will need to be rewritten from > > scratch. The benefit will be that it will truely be cleaned up, people > > will still be able to leverage the bulk of their PHP programming > > background and they can enjoy the fastest possible unicode engine we can > > provide them. > > > > PHP5 will be for the people that cannot make the jump. We will back port > > whatever we can reasonably get into PHP5. People will linger on PHP5, > > just as they are doing now with PHP4. So it goes. At least we will not > > punish the early adopters for those that are unwilling to move to the > > new version in the near future anyways. > > > > At any rate .. the time is now to make a decision on what its gonna be. > > PHP6 with BC hacks or not. > > > > regards, > > Lukas > > > >