On Friday 30 September 2011 14:11:33 ext Olivier Goffart wrote:
> Another thing that need to be taken in account is that QStringLiteral takes 
> more memory in the binary. 

Actually quite a few of the string literals we have in Creator are essentially
plain ASCII "identifiers" that are only converted to QStrings to be able to 
interface QVariantMap, QSettings etc.

I have this nagging gut feeling that it would be better for performance if 
these would take QByteArray keys instead. If someone has the desparate wish
to use more than 7 bits for his key strings (I certainly don't), the convention
could just be that the encoding is implicitly assumed to be UTF-8.

I understand that this is (a) not possible to change, and (b) would mean
falling back to the Dark Ages of std::string-with-uncertain-encoding, but still,
we are discussing making a conversion fast that could be avoided altogether
in a lot of cases by just having another API.

Andre'
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback

Reply via email to