Marc Mutz <marc.m...@kdab.com> > I'm not optimising. I'm decoupling the concept of a "QString" from the owning > implementation "QString", so that we don't need to either convert from/to > QString quite so often or you can use "foreign types" > (std::basic_string<char16_t>, char16_t[], ...) in lieu of QString. That is > important when you need to interface with 3rd-party libraries.
Think about a local aware compare which is called very very often. You don't want malloc in between. In in most cases you get an const char* or const shor* in this cases It would be nice if your interface would support UTF-8 and not only UTF-16. Incorporating ideas of http://utfcpp.sourceforge.net/ could be useful. _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
