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@xxxxxxxxxxxxx> --- 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-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
