Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31779
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 85.10.196.195 cause and error)
Message-ID: <46CAA287.5080102@pooteeweet.org>
Date: Tue, 21 Aug 2007 10:29:59 +0200
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Andi Gutmans <andi@zend.com>
CC: Derick Rethans <derick@php.net>, 
 Andrei Zmievski <andrei@gravitonic.com>,
 Antony Dovgal <antony@zend.com>, Rasmus Lerdorf <rasmus@lerdorf.com>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <1181829227.3478.3.camel@localhost.localdomain> <468E1158.2030900@lerdorf.com> <468E13C6.1070109@pooteeweet.org> <468E2009.9000703@zend.com> <10845a340707060432h6516ea5eja0995dbc974baa0a@mail.gmail.com> <468E2A9C.8030704@zend.com> <10845a340707060454t24a854dfu93aad454dd1f37ed@mail.gmail.com> <468E2F78.9090002@pooteeweet.org> <10845a340707060509u70152abctf1801324be490ed1@mail.gmail.com> <468E400E.6060005@e-novative.de> <b5f7bf6c0708200914t71ca0d34t9439d1536485ec67@mail.gmail.com> <E9E1B5C4-81FA-47A8-95A8-06D603DC1C27@gravitonic.com> <698DE66518E7CA45812BD18E807866CE92D7B0@us-ex1.zend.net> <alpine.DEB.0.98.0708210817070.4960@kossu.ez.no> <698DE66518E7CA45812BD18E807866CE92D7E2@us-ex1.zend.net> <alpine.DEB.0.98.0708210832250.4960@kossu.ez.no> <698DE66518E7CA45812BD18E807866CE92D7E6@us-ex1.zend.net>
In-Reply-To: <698DE66518E7CA45812BD18E807866CE92D7E6@us-ex1.zend.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-backendmedia-com-MailScanner-Information: Please contact the ISP for more information
X-backendmedia-com-MailScanner: Found to be clean
X-backendmedia-com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
	score=0, required 6)
X-backendmedia-com-MailScanner-From: mls@pooteeweet.org
X-Spam-Status: No
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: mls@pooteeweet.org (Lukas Kahwe Smith)

Andi Gutmans wrote:

> Maybe you guys can try with ezComponents?

So whats your target with this BC flag .. make it possible to have 
PHP4-PHP6 (unicode off) apps?

Keep in mind that the camp that is suggesting to remove the unicode flag 
is at the same time committing to back porting more things to PHP5 in a 
case per case basis. As a result users will not be left in the dust with 
PHP5.

Derick also suggested on IRC that we should focus on making PHP 5.3 as 
much forward compatible as possible, to make this even more feasible.

Remember that several people have pointed out that maintaining the 
unicode flag is more or less like maintaining two branches (in some 
respects its even harder .. in some other its less .. which probably 
evens out more or less ..). At the same time we will need to maintain 
PHP5 for quite some time anyways as PHP6 matures and people get more RAM :)

This porting effort will undoubtly benefit PHP6 in the ways you 
describe. It will help us find issues, it will help us improve the 
migration documentation. However binding this decision to actually 
porting a BIG PHP4 and a BIG PHP5 app is not feasible. We _know_ the 
increased effort in maintance, we do not know the performance impact and 
the migration time. So how can the default be that we increase the 
maintance effort in order to speed up something we do not know?

regards,
Lukas