The QLatin1String class provides a thin wrapper around an US-ASCII/Latin-1 encoded string literal. More...
#include <QLatin1String>
Note: All functions in this class are reentrant.
| QLatin1String ( const char * str ) | |
| const char * | latin1 () const |
| bool | operator!= ( const QString & other ) const |
| bool | operator!= ( const char * other ) const |
| bool | operator< ( const QString & other ) const |
| bool | operator< ( const char * other ) const |
| bool | operator<= ( const QString & other ) const |
| bool | operator<= ( const char * other ) const |
| QLatin1String & | operator= ( const QLatin1String & other ) |
| bool | operator== ( const QString & other ) const |
| bool | operator== ( const char * other ) const |
| bool | operator> ( const QString & other ) const |
| bool | operator> ( const char * other ) const |
| bool | operator>= ( const QString & other ) const |
| bool | operator>= ( const char * other ) const |
The QLatin1String class provides a thin wrapper around an US-ASCII/Latin-1 encoded string literal.
Many of QString's member functions are overloaded to accept const char * instead of QString. This includes the copy constructor, the assignment operator, the comparison operators, and various other functions such as insert(), replace(), and indexOf(). These functions are usually optimized to avoid constructing a QString object for the const char * data. For example, assuming str is a QString,
if (str == "auto" || str == "extern" || str == "static" || str == "register") { ... }
is much faster than
if (str == QString("auto") || str == QString("extern") || str == QString("static") || str == QString("register")) { ... }
because it doesn't construct four temporary QString objects and make a deep copy of the character data.
Applications that define QT_NO_CAST_FROM_ASCII (as explained in the QString documentation) don't have access to QString's const char * API. To provide an efficient way of specifying constant Latin-1 strings, Qt provides the QLatin1String, which is just a very thin wrapper around a const char *. Using QLatin1String, the example code above becomes
if (str == QLatin1String("auto") || str == QLatin1String("extern") || str == QLatin1String("static") || str == QLatin1String("register") { ... }
This is a bit longer to type, but it provides exactly the same benefits as the first version of the code, and is faster than converting the Latin-1 strings using QString::fromLatin1().
Thanks to the QString(const QLatin1String &) constructor, QLatin1String can be used everywhere a QString is expected. For example:
QLabel *label = new QLabel(QLatin1String("MOD"), this);
See also QString and QLatin1Char.
Constructs a QLatin1String object that stores str. Note that if str is 0, an empty string is created; this case is handled by QString.
The string data is not copied. The caller must be able to guarantee that str will not be deleted or modified as long as the QLatin1String object exists.
See also latin1().
Returns the Latin-1 string stored in this object.
Returns true if this string is not equal to string other; otherwise returns false.
The comparison is based exclusively on the numeric Unicode values of the characters and is very fast, but is not what a human would expect. Consider sorting user-interface strings with QString::localeAwareCompare().
This function overloads operator!=().
The other const char pointer is converted to a QString using the QString::fromAscii() function.
You can disable this operator by defining QT_NO_CAST_FROM_ASCII when you compile your applications. This can be useful if you want to ensure that all user-visible strings go through QObject::tr(), for example.
This function was introduced in Qt 4.3.
Returns true if this string is lexically less than the other string; otherwise returns false.
The comparison is based exclusively on the numeric Unicode values of the characters and is very fast, but is not what a human would expect. Consider sorting user-interface strings using the QString::localeAwareCompare() function.
This is an overloaded function.
The other const char pointer is converted to a QString using the QString::fromAscii() function.
You can disable this operator by defining QT_NO_CAST_FROM_ASCII when you compile your applications. This can be useful if you want to ensure that all user-visible strings go through QObject::tr(), for example.
This function was introduced in Qt 4.3.
Returns true if this string is lexically less than or equal to string other; otherwise returns false.
The comparison is based exclusively on the numeric Unicode values of the characters and is very fast, but is not what a human would expect. Consider sorting user-interface strings with QString::localeAwareCompare().
This is an overloaded function.
The other const char pointer is converted to a QString using the QString::fromAscii() function.
You can disable this operator by defining QT_NO_CAST_FROM_ASCII when you compile your applications. This can be useful if you want to ensure that all user-visible strings go through QObject::tr(), for example.
This function was introduced in Qt 4.3.
Constructs a copy of other.
This function was introduced in Qt 4.1.
Returns true if this string is equal to string other; otherwise returns false.
The comparison is based exclusively on the numeric Unicode values of the characters and is very fast, but is not what a human would expect. Consider sorting user-interface strings with QString::localeAwareCompare().
This is an overloaded function.
The other const char pointer is converted to a QString using the QString::fromAscii() function.
You can disable this operator by defining QT_NO_CAST_FROM_ASCII when you compile your applications. This can be useful if you want to ensure that all user-visible strings go through QObject::tr(), for example.
This function was introduced in Qt 4.3.
Returns true if this string is lexically greater than string other; otherwise returns false.
The comparison is based exclusively on the numeric Unicode values of the characters and is very fast, but is not what a human would expect. Consider sorting user-interface strings with QString::localeAwareCompare().
This is an overloaded function.
The other const char pointer is converted to a QString using the QString::fromAscii() function.
You can disable this operator by defining QT_NO_CAST_FROM_ASCII when you compile your applications. This can be useful if you want to ensure that all user-visible strings go through QObject::tr(), for example.
This function was introduced in Qt 4.3.
Returns true if this string is lexically greater than or equal to string other; otherwise returns false.
The comparison is based exclusively on the numeric Unicode values of the characters and is very fast, but is not what a human would expect. Consider sorting user-interface strings with QString::localeAwareCompare().
This is an overloaded function.
The other const char pointer is converted to a QString using the QString::fromAscii() function.
You can disable this operator by defining QT_NO_CAST_FROM_ASCII when you compile your applications. This can be useful if you want to ensure that all user-visible strings go through QObject::tr(), for example.
This function was introduced in Qt 4.3.
© 2008-2011 Nokia Corporation and/or its subsidiaries. Nokia, Qt and their respective logos are trademarks of Nokia Corporation in Finland and/or other countries worldwide.
All other trademarks are property of their respective owners. Privacy Policy
Licensees holding valid Qt Commercial licenses may use this document in accordance with the Qt Commercial License Agreement provided with the Software or, alternatively, in accordance with the terms contained in a written agreement between you and Nokia.
Alternatively, this document may be used under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation.