feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Coding style: Remove outdated section wrt nullptr

Browse Source 
Ealier we state that nullptr should be used, and that is the current
policy.

Change-Id: Id462458f36893354a4f95e086d25a946f94b495e
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Eike Ziller
2023-02-16 08:30:16 +01:00
parent 7a2023f157
commit 22a6b79f45
1 changed files with 0 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/qtcreatordev/src/coding-style.qdoc
View File

@@ -907,11 +907,6 @@
Make sure that a class uses \c{override} consistently, either for all overridden functions or Make sure that a class uses \c{override} consistently, either for all overridden functions or
for none. 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 \section3 Range-Based for-Loop
You may use range-based for-loops, but beware of the spurious detachment problem. You may use range-based for-loops, but beware of the spurious detachment problem.