Re: What is the use of "unicode.semantics" in PHP 6?

On 7/6/07, Stefan Priebsch <stefan.priebsch@e-novative.de> wrote: > IMHO backporting a lot of features to PHP4 is a major reasons for the > slow PHP5 adoption. Basically, it seems that everybody who is not using > OOP feels that PHP4 is fine for them. > > I'd say committing to backporting stuff from PHP6 to PHP5 will yield a > similar situation: very slow or no PHP6 adoption. > > BTW, can't the unicode switch be done at compile time? So one can > compile PHP6 Unicode and PHP6 non-Unicode. Then if there is a clever way > of running both engines in parallel, there should be no performance > impact inside the non-unicode engine. Since there is both versions of > the engine (that can maybe even selected by a certain statement in the > main PHP file of the application), unicode and non-unicode users are > happy. And there is only one version of PHP in the market, to conquer it > all. > > There must be a reason to upgrade to a new PHP version (usually > features, maybe performance increase etc.). But there also must be no > reason not to upgrade. But you all know this, it has been said before. > > Kind regards, > > Stefan > > -- > >e-novative> - We make IT work for you. > > e-novative GmbH - HR: Amtsgericht München HRB 139407 > Sitz: Wolfratshausen - GF: Dipl. Inform. Stefan Priebsch > > http://www.e-novative.de > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Time to put gas on the fire. Is this flag going to be removed or what? What is happening here in the background that we are not seeing ? :) -- D Do I get a buck? No so ?