Zeev Suraski wrote: > Why? A great deal of users will be running with unicode semantics > turned off, and I don't see a good reason to break source compatibility > for them. For example, if Foo Inc. wrote a module for PHP 4, and they > want to migrate to PHP 6 - it should be a simple recompile. It's OK if > we barf when they turn unicode_sematics off, but not if they don't.
What happens when the extension gets an IS_UNICODE string passed to it if they are not using zend_parse_parameters()? These strings can exist independent of the unicode semantics switch. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
