Hi Joe, As an extension it looks fine. I assume, you don't propose to use UString objects in engine and other extensions. Unfortunately, it's yet another incomplete solution.
It won't allow Unicode strings as array keys; concatenation using "." (probably may be done), no auto-conversion from/to script/output encoding, no auto-conversion of strings coming from database extensions, etc The "right" approach, would be extending zend_string with "encoding" and then adopting near all functions working with zend_string to take "encoding" into account. But, of course, this is going to lead to much more complicated solution (with some slowdown). If we don't care about complete solution, UString proposal may make sense at lest as a faster replacement of ext/mbstring. Thanks. Dmitry. On Tue, Oct 21, 2014 at 11:06 AM, Joe Watkins <pthre...@pthreads.org> wrote: > Morning internalz, > > https://wiki.php.net/rfc/ustring > > This is the result of work done by a few of us, we won't be > opening any > vote in a fortnight. We have a long time before 7, there is no rush > whatever. > > Now seems like a good time to start the conversation so we can > hash out > the details, or get on with other things ;) > > Cheers > Joe > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
