1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix a minor grammar glitch in new string / byte-array doc note

Browse Source 
Amends 8845caa057cfcf54f7d46621adb3393c13747ffb.

Change-Id: I4bf09b9c1fff52815de58070fbe4ff0c08eff53f
Reviewed-by: Marc Mutz <marc.mutz@kdab.com>
 
 
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
This commit is contained in:
Edward Welbourne 2019-06-04 19:49:12 +02:00 committed by Marc Mutz
parent 0624c99ea3
commit 3619e87ba1
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/corelib/tools/qbytearray.cpp
View File

@ -1439,7 +1439,7 @@ QByteArray &QByteArray::operator=(const char *str)
\note Before Qt 5.14 it was possible to use this operator to access \note Before Qt 5.14 it was possible to use this operator to access
a character at an out-of-bounds position in the byte array, and a character at an out-of-bounds position in the byte array, and
then assign to such position, causing the byte array to be then assign to such a position, causing the byte array to be
automatically resized. Furthermore, assigning a value to the automatically resized. Furthermore, assigning a value to the
returned QByteRef would cause a detach of the byte array, even if the returned QByteRef would cause a detach of the byte array, even if the
byte array has been copied in the meanwhile (and the QByteRef kept byte array has been copied in the meanwhile (and the QByteRef kept

2
src/corelib/tools/qstring.cpp
View File

@ -5800,7 +5800,7 @@ QString QString::trimmed_helper(QString &str)
\note Before Qt 5.14 it was possible to use this operator to access \note Before Qt 5.14 it was possible to use this operator to access
a character at an out-of-bounds position in the string, and a character at an out-of-bounds position in the string, and
then assign to such position, causing the string to be then assign to such a position, causing the string to be
automatically resized. Furthermore, assigning a value to the automatically resized. Furthermore, assigning a value to the
returned QCharRef would cause a detach of the string, even if the returned QCharRef would cause a detach of the string, even if the
string has been copied in the meanwhile (and the QCharRef kept string has been copied in the meanwhile (and the QCharRef kept