Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37434
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain users.sourceforge.net from 213.197.162.99 cause and error)
Message-ID: <48988.78.61.224.253.1209918881.nsm@avilys.eik.lt>
In-Reply-To: <4BD5A050-02F2-46BD-B867-FA8CA12FF1BD@macvicar.net>
References: <4BD5A050-02F2-46BD-B867-FA8CA12FF1BD@macvicar.net>
Date: Sun, 4 May 2008 19:34:41 +0300 (EEST)
To: internals@lists.php.net
User-Agent: NaSMail/1.4
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] Removal of unicode_semantics
From: tokul@users.sourceforge.net ("Tomas Kuliavas")

> We've discussed this a few times in the past and it's time to make a
> final decision about its removal.
>
> I think most people have agreed that this is the way forward but no
> one has produced a patch. I have a student working on unicode
> conversion for the Google Summer of Code and this would help make it
> simpler.

unicode_semantics=on breaks backwards compatibility in scripts that have
implemented multiple character set support in current PHP setups.

If setting is removed, instead of maintaining at least some bits of
backwards compatibility and doing some additional work, you force massive
code rewrites in scripts that depend on working charset support and more
work for people, who use interpreter.

Every time somebody proposes removal of this setting, they claim that
majority agreed on it when there is no agreement on anything. People only
defended own positions and we had other flame about unicode_semantics.

-- 
Tomas