From: Rob Landley <rob@landley.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Eduardo Valentin <eduardo.valentin@ti.com>
Subject: Re: [patch] Documentation: allow multiple return statements per function
Date: Wed, 15 May 2013 18:00:35 -0500 [thread overview]
Message-ID: <1368658835.18069.250@driftwood> (raw)
In-Reply-To: <20130515172021.GA304@elgon.mountain> (from dan.carpenter@oracle.com on Wed May 15 12:20:21 2013)
On 05/15/2013 12:20:21 PM, Dan Carpenter wrote:
> 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>
Ack, please forward to trivial tree.
Rob
next prev parent reply other threads:[~2013-05-16 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 17:20 [patch] Documentation: allow multiple return statements per function Dan Carpenter
2013-05-15 23:00 ` Rob Landley [this message]
2013-05-16 14:52 ` Eduardo Valentin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1368658835.18069.250@driftwood \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=eduardo.valentin@ti.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox