On Tue, 17 Jul 2007, Andi Gutmans wrote: > Hmm I don't quite understand what bad code vs. good code plays here. > Wordpress is one of the most popular applications out there so it's got > huge value to our community. I bet there's a huge amount of PHP > applications who's source code is of the same quality or worse. Anyway, > the issues I have seen would also be relevant to what you call "good" > code but again, when it comes to compatibility, I don't quite know why > that will play a big role. > > I am talking about porting to both unicode_semantics=off and on. This > will give us a good understanding of the difference of the modes and > where we're at. I bet most people who are voicing their opinions have > actually not tried to write a sizeable application with PHP 6 and also > tried to run an existing one on PHP 6 > (unciode_semantics=on).
I hope you are not suggesting to port them to both modes? Why on earth should an application support both unicode=off and unicode=on? That's exactly the thing that some of us are so afraid of and want to prevent as this just annoys more and more PHP users that have to deal with this stuff. And as mentioned before, having both modes is *way* worse than having to real with register_globals on/off or magic_quotes, as those two cases could atleast be handled in user space. regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
