On 06/09/06, M. Sokolewicz <[EMAIL PROTECTED]> wrote:
My personal opinion, as humble as it may be, is that it's pure bullshit to even give the chance of disabling it. WHY in hell's name would you want to give hoster's the choice? I can see a part of the hosts disabling it to "give an easy transition" while another part of the hosts enable it to "give the new features a chance". If Unicode support it supposed to be such a big part of the while PHP6 release then why do you give the option of disabling it? you're breaking away part of the MAIN reason why people would want to upgrade in the first place. Just imagine what a mess it would be if you had given the choice of "disabling" the OOP support in PHP5. Be very very very glag you didn't do that, and as such I'd suggest not doing something equally drastic in PHP6.
I agree on this. From my reading of some the issues around unicode you are far better off simply saying PHP6 is unicode only. A lot of scripts that use register_globals and any number of deprecated features are simply not going to work with PHP6 anyway. There is another side to this. For those developers who are NOT unicode aware they will be wondering what all the fuss is about. They are probably the same developers who wonder why anyone would want discrete setters/getters in PHPs OOP. I think it is these people who will have the biggest headache. Many ISPs install CPanel or Plesk or whatever and never configure things anyway. Actively promoting ISPs capable of taking PHP6 and running with it would be a nice way to show/prove the value of PHP6. What would be far more useful would be a very clear set of documentation regarding the steps needed to take to move a PHP based application forward into the Unicode'd world. Regards, Richard Quadling. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"
