It does make the engine more complicated though, because we can't just
check for UG(unicode) and expect all identifiers to be of the same
type. We would actually need to amend a lot of API functions to include
passing the identifier type along, e.g. zend_get_active_function()
would need to return the identifier type along with the identifier
itself.
-Andrei
On Aug 16, 2005, at 1:36 PM, Andi Gutmans wrote:
IIRC if unicode_semnantics=on, we agreed to use Unicode for array
offsets and properties (and do auto-conversion). however, if unicode =
off, we should not do auto conversion but allow php users to manually
create unicode data. when it comes to arrays we agreed that in this
case they can use strings and unicode as they wish (makes sense for
apps that can't make the complete move but can unicode-enable some of
the app, for example, a web service).
so bottom line, i dont think we can expect class name and property to
be in the same encoding unless we hard code it, but i like the
flexibility of being able to use unicode strings when
unicode_semantics is off....
(this took me far too long to write :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
