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.
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. Since you are turning it on, Im not turning it on.. redistributable application are at mercy of the server configuration.
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.
Don't forget that you can still use most of the Unicode features even with unicode.semantics=off,
if it were INI_PER_DIR maybe I can, nowdays is nto possible.
so it's up to you to decide.
With the current situation the only alternative is to keep applications backward compatible with PHP4 and PHP5 and forget PHP6 . Hoepfully this project will learn something with the previuos experiences ( PHP5 adoption anyone? ) and think in a reasoanble backward compatibility policy. 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. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
