Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31737
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.162.182 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=Hfm2qDadcaxj99n9F3ry1kayJ2rRnkAmVLzAZEXnLFMF9Uggg7seyer4VZiL7JILAai79Hb/cOsfY0VhqUHfY7v6yH8stw85VfiJOG1RHSg5izYWZMVGtcxY4LjlnzYJ3qCyuQbR6VkjOKGkvBht/uDB4Nw4/+roYB1Uoz+YwZc=
Message-ID: <b5f7bf6c0708200914t71ca0d34t9439d1536485ec67@mail.gmail.com>
Date: Mon, 20 Aug 2007 12:14:55 -0400
Sender: david.coallier@gmail.com
To: "Stefan Priebsch" <stefan.priebsch@e-novative.de>
Cc: RQuadling@googlemail.com, "Lukas Kahwe Smith" <mls@pooteeweet.org>, 
	"Antony Dovgal" <antony@zend.com>, 
	"Rasmus Lerdorf" <rasmus@lerdorf.com>, 
	"Derick Rethans" <derick@php.net>, 
	"Cristian Rodriguez" <judas.iscariote@gmail.com>, 
	internals@lists.php.net
In-Reply-To: <468E400E.6060005@e-novative.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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>
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: davidc@php.net ("David Coallier")

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=FCnchen 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 ? :)


--=20
D
Do I get a buck? No so ?