diff options
author | Thiago Macieira <thiago.macieira@intel.com> | 2021-10-12 09:42:23 -0700 |
---|---|---|
committer | Oswald Buddenhagen <oswald.buddenhagen@gmx.de> | 2021-10-22 04:30:53 +0000 |
commit | f9139b19bff2f1bc5cbc937c779a5e584dcdafc7 (patch) | |
tree | 52129de3e774fabded166c999bf28250ab738e39 /examples/widgets/widgets/tooltips/shapeitem.cpp | |
parent | 5bc315fbe204de6e629896e19d7297bcb8c01802 (diff) |
QLatin1String: harmonize null byte handling with the rest of QString
After the introduction of QByteArrayView, all the QString::fromXxx
overloads and the constructor will include the null bytes inside
QByteArrays and so will QLatin1Strings created from QByteArrayViews.
This was the lone stand-out that wasn't fixed in 6.0, so do it now.
[ChangeLog][Important Behavior Changes] Since Qt 6.0, all QString and
QLatin1String methods consuming QByteArray and QByteArrayView objects
will include any embedded null bytes and treat them as U+0000 Unicode
characters, whereas in Qt 4.x and 5.x, they would stop at the first null
byte like bare C strings. Qt 6.3 contains a fix for a couple of the
methods that mistakenly persisted the old behavior in 6.0-6.2, namely
the QLatin1String constructor from QByteArray and the equality and
inequality operators between QByteArray and QString.
Task-number: QTBUG-97451
Change-Id: Icb2516126f674e7b8bb3fffd16ad5621cf3e64ec
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
Diffstat (limited to 'examples/widgets/widgets/tooltips/shapeitem.cpp')
0 files changed, 0 insertions, 0 deletions