Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30179
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 204.11.219.139 cause and error)
Message-ID: <46715887.4010306@lerdorf.com>
Date: Thu, 14 Jun 2007 16:02:31 +0100
User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326)
MIME-Version: 1.0
To:  jani.taskinen@iki.fi
CC:  internals@lists.php.net
References: <1181829227.3478.3.camel@localhost.localdomain>
In-Reply-To: <1181829227.3478.3.camel@localhost.localdomain>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Jani Taskinen wrote:
> During Derick's talk about PHP 6 at PHP Vikinger, I started to wonder
> what exactly was the reasoning behind adding something like
> "unicode.semantics" option. Derick didn't remember, neither did I.
> 
> Apparently it's another one of these "register_globals" or
> "magic_quotes_*" directives we'll remove in PHP 7? :D
> 
> I mean, if PHP 6 is about unicode, why upgrade to PHP 6 and disable it?
> Just stay with PHP 5 then..

That's exactly why we need the toggle.  We don't want to encourage
people to stay with an older version.  We have enough trouble getting
people from 4 to 5 today, why build in an automatic excuse for people to
stay with 5 when all development moves to 6?  If all their PHP 5-based
code works flawlessly in PHP 6, the adoption of PHP 6 will be quicker.

-Rasmus