Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37445 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52741 invoked from network); 5 May 2008 07:51:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 May 2008 07:51:35 -0000 Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 89.208.40.236 mail.daylessday.org Linux 2.6 Received: from [89.208.40.236] ([89.208.40.236:45640] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 77/82-40102-68CBE184 for ; Mon, 05 May 2008 03:51:35 -0400 Received: from [192.168.3.91] (unknown [212.42.62.198]) by daylessday.org (Postfix) with ESMTP id 0CEF06401EC; Mon, 5 May 2008 11:51:32 +0400 (MSD) Message-ID: <481EBC7C.2040806@daylessday.org> Date: Mon, 05 May 2008 11:51:24 +0400 User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Tomas Kuliavas CC: internals@lists.php.net References: <4BD5A050-02F2-46BD-B867-FA8CA12FF1BD@macvicar.net> <48988.78.61.224.253.1209918881.nsm@avilys.eik.lt> In-Reply-To: <48988.78.61.224.253.1209918881.nsm@avilys.eik.lt> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Removal of unicode_semantics From: tony@daylessday.org (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. -- Wbr, Antony Dovgal