Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30183
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 83.243.58.163 cause and error)
To: jani.taskinen@iki.fi
Cc: internals@lists.php.net
In-Reply-To: <1181829227.3478.3.camel@localhost.localdomain>
References: <1181829227.3478.3.camel@localhost.localdomain>
Content-Type: text/plain
Date: Thu, 14 Jun 2007 17:23:14 +0200
Message-ID: <1181834594.8607.1.camel@johannes.nop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] What is the use of "unicode.semantics" in PHP 6?
From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi Jani,

On Thu, 2007-06-14 at 16:53 +0300, 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.

The reason was to "keep BC"

> 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..

- The ini Setting changes the behaviour of the code in a quite
  drastic way. This is even worse then magic_quotes which could 
  be fixed by using some prepending file removing/adding slashes
  depending on the setting.

- The UG(unicode) checks in the code make maintenance way harder.

- This feature doesn't bring BC - there will still be enough BC
  breaks.

- I guess we're adding a few thousand UG(unicode) checks during
  each request which certainly cost a bit performance

Conclusion: Let's remove that damn setting.

johannes