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.
Why don't you go ahead and make a list of those exacty issues then? We
can then see how to fix those issues. That's much more useful then just
posting to the mailinglist when you don't agree with something. From
what I've seen with my code base, the changes that I have to do are
minimal once some (internal) functions are fixed up.
If I remain silent, others will have arguments that "everybody agrees on
removal of unicode_semantics".
<snip>
I can bypass it by adding one line to every script that operates with
binary strings, but where are warranties that you won't dump declare()
support just like you dump unicode_semantics. What happens to your new
Unicode aware string functions, if I lie about strings' charset to PHP
interpreter? mb_strlen can't calculate correct $string length even when I
set correct charset in mb_strlen() arguments. If above code works as I
want in PHP6 unicode_semantics=on, mb_strlen($string,'utf-8') returns 2
and not 1.
That sounds like just the sort of edge case that Derick is suggesting needs
logging for fixing up. unicode_semantics=on is just another bodge to to make
it happen rather than a solution. I think I understand your description, and
to my eyes it looks like a unicode bug that needs addressing?
We have been maintaining two code bases for a long time now - PHP4 and PHP5.
Now that PHP4 is being shelved finally those of us who have had to maintain
compatibility with PHP4 can now move on and address the problems of PHP5/PHP6
compatibility. So from *MY* point of view unicode_semantics=on is creating a
THIRD case to have to manage? PLEASE can someone take charge and at least get
PHP6 moving forward to a stable alpha so that we have something users can be
happy to test against!
PHP5 = code sets
PHP6 = Unicode
--
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
