path: root/tests/auto/corelib/io/qfile/tst_qfile.cpp
diff options
authorMarc Mutz <>2017-03-10 15:27:40 +0100
committerMarc Mutz <>2017-03-12 17:41:16 +0000
commit75f5e2bef2ab942f89d5d025ecd45ee4d18e3d57 (patch)
tree0b6da8d12aa9812b100f72cdd738c8be94a19254 /tests/auto/corelib/io/qfile/tst_qfile.cpp
parent63a39927a098aeb60a03b77361502b5be7659f1d (diff)
Deprecate QString::null
It's a Qt 3 compatibility vehicle, and as such inherits the now-alien property to distinguish empty and null strings. Particularly worrisome is the following asymmetry: QString("") == QString::null // false QString("") == QString(QString::null) // true Instead of fixing this behavior, recognize that people might use it as a weird way to call isNull(), albeit one that once was idiomatic, and simply deprecate everything that deals with QString::null. [ChangeLog][QtCore][QString] QString::null is now deprecated. When used to construct a QString, use QString() instead. When used to compare to a QString, replace with QString::isNull(). Change-Id: I9f7e84a92522c75666da15f49324c500ae93af42 Reviewed-by: Thiago Macieira <> Reviewed-by: Anton Kudryavtsev <>
Diffstat (limited to 'tests/auto/corelib/io/qfile/tst_qfile.cpp')
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/auto/corelib/io/qfile/tst_qfile.cpp b/tests/auto/corelib/io/qfile/tst_qfile.cpp
index 57e197aa83..3620043eb1 100644
--- a/tests/auto/corelib/io/qfile/tst_qfile.cpp
+++ b/tests/auto/corelib/io/qfile/tst_qfile.cpp
@@ -1684,7 +1684,7 @@ void tst_QFile::isSequential()
void tst_QFile::encodeName()
- QCOMPARE(QFile::encodeName(QString::null), QByteArray());
+ QCOMPARE(QFile::encodeName(QString()), QByteArray());
void tst_QFile::truncate()