From 22a6b79f4577d3500914c9d4da2430a21c111ab0 Mon Sep 17 00:00:00 2001 From: Eike Ziller Date: Thu, 16 Feb 2023 08:30:16 +0100 Subject: [PATCH] Coding style: Remove outdated section wrt nullptr Ealier we state that nullptr should be used, and that is the current policy. Change-Id: Id462458f36893354a4f95e086d25a946f94b495e Reviewed-by: hjk --- doc/qtcreatordev/src/coding-style.qdoc | 5 ----- 1 file changed, 5 deletions(-) diff --git a/doc/qtcreatordev/src/coding-style.qdoc b/doc/qtcreatordev/src/coding-style.qdoc index ba2e75aae11..1aed25bc3ef 100644 --- a/doc/qtcreatordev/src/coding-style.qdoc +++ b/doc/qtcreatordev/src/coding-style.qdoc @@ -907,11 +907,6 @@ Make sure that a class uses \c{override} consistently, either for all overridden functions or for none. - \section3 Nullptr - - All compilers support \c{nullptr}, but there is no consensus on using it. If in doubt, ask - the maintainer of the module whether they prefer using \c{nullptr}. - \section3 Range-Based for-Loop You may use range-based for-loops, but beware of the spurious detachment problem.