| 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
| ||
|
Date: Fri, 19 Dec 2014 14:36:28 +0100 From: Alexander Holler <holler@...oftware.de> To: Jonathan Corbet <corbet@....net> Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org, Alexander Holler <holler@...oftware.de> Subject: [RFC PATCH] CodingStyle: remove what nowadays might be considered polemic In times where things like checkpatch do exist and are mandated to be used, it would be easy to warn if too many levels of indentation are used (e.g. by counting leading tabs). The paragraph before already says that more than 3 levels of indentation are bad, so the (removed) sentence nowadays only smells like an additional excuse or polemic (because you still could use an unholy number of e.g. 7 indentations, even within the limit of 80 chars). Signed-off-by: Alexander Holler <holler@...oftware.de> --- Documentation/CodingStyle | 4 ---- 1 file changed, 4 deletions(-) diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle index 618a33c..8e96b14 100644 --- a/Documentation/CodingStyle +++ b/Documentation/CodingStyle @@ -31,10 +31,6 @@ the code move too far to the right, and makes it hard to read on a more than 3 levels of indentation, you're screwed anyway, and should fix your program. -In short, 8-char indents make things easier to read, and have the added -benefit of warning you when you're nesting your functions too deep. -Heed that warning. - The preferred way to ease multiple indentation levels in a switch statement is to align the "switch" and its subordinate "case" labels in the same column instead of "double-indenting" the "case" labels. E.g.: -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists