Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19491 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44906 invoked by uid 1010); 7 Oct 2005 21:24:50 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 44891 invoked from network); 7 Oct 2005 21:24:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Oct 2005 21:24:50 -0000 X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:47724] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 41/A4-54476-F97E6434 for ; Fri, 07 Oct 2005 17:24:49 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j97LObEN028342; Fri, 7 Oct 2005 23:24:37 +0200 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.12.11/8.12.11) with ESMTP id j97LOXek028333; Fri, 7 Oct 2005 23:24:35 +0200 Date: Fri, 7 Oct 2005 23:24:34 +0200 (CEST) X-X-Sender: derick@localhost To: Rasmus Lerdorf cc: PHP Developers Mailing List In-Reply-To: <4346E3F2.30904@lerdorf.com> Message-ID: References: <99dd4f75f4ceebfe1c980cf439e97416@gravitonic.com> <4346E00A.8020504@prohost.org> <4346E0C5.3090001@lerdorf.com> <4346E3F2.30904@lerdorf.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at jdi-ict.nl Subject: Re: [PHP-DEV] Unicode Implementation From: derick@php.net (Derick Rethans) On Fri, 7 Oct 2005, Rasmus Lerdorf wrote: > > What is wrong with PHP 5.1? People don't *have* to upgrade to the > > unicode enabled PHP if they don't want to. And it would probably be > > "nice" to have that mode for some users, but should that be over our own > > back with multiple implementations of everything? > > The "don't upgrade" argument doesn't work. Unless we commit to having > two major versions forever where we will add new features. That is a > possibility as well of course. Have 2 trees. Unicode-PHP and > non-Unicode-PHP and everything that is not Unicode-related will need to > be committed to both. yeah, and if that allows us to cleanup PHP 6 for real, then I am not even sure if that is such a bad solution. Ofcourse, the new cool features would go to PHP 6 only, but that's now the same wih 4.4 and 5.1 too anyway. But I don't want to jump too quickly to conclusions about the UNicode speed and BC breakage. All I tested is raw string functions and there is no way that the whole application slows down as much as we saw in the few benchmarks that I run. Besides that, we can probably optimize the string functions somewhat anyway. I'd like to see the speed decrease for real applications too. regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org