Hi Christian, On Thu, 2007-05-24 at 05:19 -0400, Cristian Rodriguez wrote: > 2007/5/22, Andrei Zmievski <[EMAIL PROTECTED]>: > > Nobody is breaking your code. > > Yes, it does break code, unicode.semantics is ZEND_INI_SYSTEM, hence > I cannot even turn it off with htaccess.
I think it was once discussed to make it PER_DIR depending on the implementation problems but I'm not sure about the results, please check the archives. > > You are free to use unicode.semantics > > or turn it off. > > No, I cant. redistributable applications (most opensource code out there) > cannot > > 1. rely on having php 5.2.1 or later , please see the real world out > there.. very few hosts has PHP5. Most Masshosters I know in Germany offer PHP 5 (most times you can even switch between PHP 4 and 5) and I guess in other countries it's the same. People running stone-age systems can only use stone-age software. > Since you are turning it on, > > Im not turning it on.. redistributable application are at mercy of the > server configuration. If you don't turn it on it will break more PHP 6 applications and will still have a few BC issues. > > I assume that you are > > willing to make some changes to your code in order to take advantage > > of the new features. > > Yes but not breaking backward compatibility. We can't bring PHP forward and keep 100% BC. And many people (especially outside the US, like Asian countries) need full unicode support. > With the current situation the only alternative is to keep > applications backward compatible with PHP4 and PHP5 and forget PHP6 . I was able to run PHP 4 compatible applications on PHP 6 in unicode mode. For your problem instead of using something like the b prefix for strings or (binary) cast you can use unicode_encode() to convert from internal encoding to a binary string using the proper encoding. For PHP 4 you just define the function yourself and simply return the string. http://php.net/unicode_encode > Hoepfully this project will learn something with the previuos > experiences ( PHP5 adoption anyone? ) and think in a reasoanble > backward compatibility policy. This is a different story: From what I'm reading Unicode support is for many people way more interesting than many things introduced with PHP 5. ("syntactical sugar") And another thing: I'm currently creating some statistics about PHP versions used to run average applications since these statistics from netcraft pinging hosts are nice but they don't show which of these hosts are really used and where new software is being installed. Currently my statistics aren't really significant but show PHP 5 usage > 60% (PHP 5.2 is around 50% of all used versions) with an average application - I'll post all information about that once I trust the statistics more (more data...) > ps: I know you will tell me that people should use fastcgi..and > blabla.. sure. I agree.. but that is not what the real world out there > uses. > > Always concerned of the project direction. > Sincerly > Cristian. > johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
