Re: Removal of unicode_semantics

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. 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.

And leaving unicode_semantics in will make it so web application developers like myself, who distribute their applications to be installed on people's own servers, have to write two different versions of their software to support the switch being on or off because of the major differences in the language based on an ini setting. Not only is there twice the code in PHP's codebase, there's twice the code in the codebases for people like me. But, we've been through this discussion before. I've already stated my opinions. +1 to removing this. -- Jeremy Privett C.E.O. & C.S.A. Omega Vortex Corporation http://www.omegavortex.net Please note: This message has been sent with information that could be confidential and meant only for the intended recipient. If you are not the intended recipient, please delete all copies and inform us of the error as soon as possible. Thank you for your cooperation.