Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37460
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain bitxtender.com from 80.237.132.12 cause and error)
Cc: Tomas Kuliavas <tokul@users.sourceforge.net>,
 internals@lists.php.net
Message-ID: <6F1F3735-B012-438D-874B-40BB67382F0A@bitxtender.com>
To: Antony Dovgal <tony@daylessday.org>
In-Reply-To: <481EBC7C.2040806@daylessday.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 5 May 2008 13:56:41 +0200
References: <4BD5A050-02F2-46BD-B867-FA8CA12FF1BD@macvicar.net> <48988.78.61.224.253.1209918881.nsm@avilys.eik.lt> <481EBC7C.2040806@daylessday.org>
Subject: Re: [PHP-DEV] Removal of unicode_semantics
From: dz@bitxtender.com (=?ISO-8859-1?Q?David_Z=FClke?=)

Am 05.05.2008 um 09:51 schrieb Antony Dovgal:

> On 04.05.2008 20:34, Tomas Kuliavas wrote:
>>> 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.
>
> That is correct, removing The Switch does cause some backward  
> compatibility breakage.
> But The Switch does NOT fix it, that's the problem: you would still  
> have to fix your applications to work with unicode_semantics both  
> OFF and ON, i.e. it causes _2x more_ trouble.
>
>> Every time somebody proposes removal of this setting, they claim that
>> majority agreed on it when there is no agreement on anything.
> The majority of active developers have agreed that the switch would  
> cause more harm than good.
> That's the fact.

And that's the word. +10000000. Lets get rid of it and move on.


David