Hi, On Mon, 2007-07-09 at 15:33 -0700, Stanislav Malyshev wrote: > Fixing unicode=on does not remove the IS_STRING/IS_UNICODE duality. We > still have two kinds of data - unstructured bit stream and structured > text.
But we still have the mess that most internal structures (function tables, class tables, ...) either hold an IS_STRING or IS_UNICODE depending on a configuration option - just check the amounts of UG(unicode)?IS_UNICODE:IS_STIRNG (that one even got a macro ZEND_STR_TYPE) kind of checks - these make the code way harder to read and maintain. And again: It is as easy to run PHP 5 and PHP 6 on the same host as PHP 6 with unicode and PHP 6 w/o so I can't see a BC benefit of that setting but I can see that this gives us two products with the same name - PHP 6. And that's bad. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
