Tidy nullptr usage

Move away from using 0 as pointer literal.

Done using clang-tidy. This is not complete as
run-clang-tidy can't handle all of qtbase in one go.

Change-Id: I1076a21f32aac0dab078af6f175f7508145eece0
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Reviewed-by: Lars Knoll <lars.knoll@qt.io>

1 files changed, 5 insertions, 5 deletions

diff --git a/src/network/access/qhttpnetworkreply.cpp b/src/network/access/qhttpnetworkreply.cpp
index a8b635c45a..af456c3607 100644
--- a/src/network/access/qhttpnetworkreply.cpp
+++ b/src/network/access/qhttpnetworkreply.cpp
@@ -330,12 +330,12 @@ QHttpNetworkReplyPrivate::QHttpNetworkReplyPrivate(const QUrl &newUrl)
       currentlyUploadedDataInWindow(0),
       totallyUploadedData(0),
       removedContentLength(-1),
-      connection(0),
+      connection(nullptr),
       autoDecompress(false), responseData(), requestIsPrepared(false)
       ,pipeliningUsed(false), spdyUsed(false), downstreamLimited(false)
-      ,userProvidedDownloadBuffer(0)
+      ,userProvidedDownloadBuffer(nullptr)
 #ifndef QT_NO_COMPRESS
-      ,inflateStrm(0)
+      ,inflateStrm(nullptr)
 #endif
 
 {
@@ -375,8 +375,8 @@ void QHttpNetworkReplyPrivate::clearHttpLayerInformation()
 // TODO: Isn't everything HTTP layer related? We don't need to set connection and connectionChannel to 0 at all
 void QHttpNetworkReplyPrivate::clear()
 {
-    connection = 0;
-    connectionChannel = 0;
+    connection = nullptr;
+    connectionChannel = nullptr;
     autoDecompress = false;
     clearHttpLayerInformation();
 }