| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <152114372879.3142.8833111074324091904.stgit@taos>
Date: Thu, 15 Mar 2018 15:04:02 -0500
From: Gary R Hook <gary.hook@....com>
To: linux-doc@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, corbet@....net
Subject: [PATCH v2] Documentation/CodingStyle: Add an example for braces
Add another example of required braces when using a compound statements.
Signed-off-by: Gary R Hook <gary.hook@....com>
---
Changes since v1:
- Move the new example up, and make it more generic
Documentation/process/coding-style.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index a20b44a40ec4..fcef0b4b59d0 100644
--- a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -188,6 +188,15 @@ and
else
do_that();
+Do use braces when a body is more complex than a single simple statement:
+
+.. code-block:: c
+
+ if (condition) {
+ if (another_condition)
+ do_something();
+ }
+
This does not apply if only one branch of a conditional statement is a single
statement; in the latter case use braces in both branches:
Powered by blists - more mailing lists