Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30251
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.235.23.12 as permitted sender)
To: internals@lists.php.net
Date: Tue, 19 Jun 2007 16:13:31 +0200
Message-ID: <6sof73dj69ldpspfc5ukrc58qr9ckbin2b@4ax.com>
References: <1181829227.3478.3.camel@localhost.localdomain> <7d5a202f0706141844l3c75b556hdbecbcd5a43747c9@mail.gmail.com> <4671F184.2020401@lerdorf.com>
In-Reply-To: <4671F184.2020401@lerdorf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: penguin@php.net (Peter Brodersen)

On Fri, 15 Jun 2007 02:55:16 +0100, in php.internals
rasmus@lerdorf.com (Rasmus Lerdorf) wrote:

>Those same shared hosting companies would never upgrade to PHP 6 if we
>forced unicode semantics on them breaking legacy apps and that would
>force us to maintain PHP 5 forever.

On the other hand I feel a bit sad that if I want to write perfectly
good portable PHP 6 code that is only intended to work under PHP 6 I
still have to check for different configuration settings.

I think we were really close to get out of the
if(get_magic_quotes_gpc()) "requirement" but now it has been replaced
with a new one. Even if a developer would write (portable) PHP 6 only
code.


Of course, configurations could contain a lot of other obscure
settings that might have influence on the script but none as
widespread as the difference in magic_quotes settings.

--=20
- Peter Brodersen