On Tue, June 19, 2007 2:44 pm, Rasmus Lerdorf wrote: > It comes down to predicting the future. Whichever way we go, the > decision is going to be second-guessed. If we have critical mass for > a > clean BC break, then I am ok with it. For me personally it would make > things a bit easier, but I think it would be a long long time before > we > saw any large hosts out there switch to a PHP 6 that can't run common > PHP 5 apps.
If they switch to 6 with unicode off, and never ever get around to turning unicode on, will it really be any better? They'll just be running some weird-o setup that causes all kinds of bugs and issues and you'll have users with php 6 apps that won't work in php 6 and who submit bogus bug reports about it, because of the setting. A clean break is probably better, especially if it makes php 6 much more maintainable. Large-scale hosts won't switch to 6 any faster than they switched to 5, unless there are ZERO BC breaks. And nobody can guarantee zero breaks, because there are always buglets. The effort to have unicode off in 6 is probably larger than the effort to document what needs to be done to a PHP 5 app to make it be 6-friendly, or even write tools to auto-convert the buik of a script. If unicode semantics are "on" what exactly is borked in PHP 5? Can that be fixed to be BC without resorting to this toggle? -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
