Documentation/CodingStyle: allow multiple return statements per function

A surprising number of newbies interpret this section to mean that only
one return statement is allowed per function.  Part of the problem is that
the "one return statement per function" rule is an actual style guideline
that people are used to from other projects.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Eduardo Valentin <eduardo.valentin@ti.com>
Cc: Rob Landley <rob@landley.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Dan Carpenter 2013-07-03 15:08:08 -07:00 committed by Linus Torvalds
parent e68e96d2a7
commit b57a0505e7
1 changed files with 2 additions and 1 deletions

View File

@ -389,7 +389,8 @@ Albeit deprecated by some people, the equivalent of the goto statement is
used frequently by compilers in form of the unconditional jump instruction. used frequently by compilers in form of the unconditional jump instruction.
The goto statement comes in handy when a function exits from multiple The goto statement comes in handy when a function exits from multiple
locations and some common work such as cleanup has to be done. locations and some common work such as cleanup has to be done. If there is no
cleanup needed then just return directly.
The rationale is: The rationale is: