Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30693
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain gravitonic.com from 204.11.219.139 cause and error)
In-Reply-To: <468E400E.6060005@e-novative.de>
References: <1181829227.3478.3.camel@localhost.localdomain>	 <7d5a202f0707060224oa64dfeaw2c7ee17a735648f9@mail.gmail.com>	 <alpine.DEB.0.98.0707061132430.22750@kossu.ez.no>	 <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>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-ID: <490F2AC8-6078-44EA-9FC9-F67A0C780963@gravitonic.com>
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
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Jul 2007 14:38:03 -0700
To: Stefan Priebsch <stefan.priebsch@e-novative.de>
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: andrei@gravitonic.com (Andrei Zmievski)

Yes, backporting major features from PHP 6 to 5 will slow down PHP 6 =20
adoption, and I'd like to avoid it if possible.

There is a way to run two engines side by side, by the way: in =20
separate instances of Apache. It's really not that complicated.

-Andrei


On Jul 6, 2007, at 6:13 AM, Stefan Priebsch 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 =20
> 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 =20
> 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 =20
> 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
>
> --=20
>> 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
>
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php