From: Josh Triplett <josh@joshtriplett.org>
To: Joe Perches <joe@perches.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CodingStyle: Add a chapter on conditional compilation
Date: Mon, 3 Nov 2014 10:05:28 -0800 [thread overview]
Message-ID: <20141103180528.GA9026@jtriplet-mobl1> (raw)
In-Reply-To: <1415036860.17743.25.camel@perches.com>
On Mon, Nov 03, 2014 at 09:47:40AM -0800, Joe Perches wrote:
> On Mon, 2014-11-03 at 11:46 -0500, Jonathan Corbet wrote:
> > On Wed, 29 Oct 2014 11:15:17 -0700
> > Josh Triplett <josh@joshtriplett.org> wrote:
> >
> > > Document several common practices and conventions regarding conditional
> > > compilation, most notably the preference for ifdefs in headers rather
> > > than .c files.
> >
> > OK, I've picked this one up for my 3.19 docs pull.
>
> I think that Al Viro's suggestion from awhile ago:
>
> https://lkml.org/lkml/2013/3/20/388
>
> could still be in CodingStyle somewhere or in
> another document like CodingStyleSuggestions.
I think that text needs some cleanup to better fit CodingStyle, but the
intent and recommendations definitely ought to go in. A few of those
seem too far down the road of "don't stuff beans up your nose", and some
of them need shortening (just "don't put an else after an if condition
ending with break or return; remember to handle errors via break,
return, or continue, and outdent the subsequent code").
> Another thing that could go is the suggestion to
> use Lindent.
>
> https://lkml.org/lkml/2013/2/11/390
Agreed completely. We might consider coming up with settings for
clang-format, which seems like a far more capable replacement that
actually understands C.
- Josh Triplett
next prev parent reply other threads:[~2014-11-03 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 18:15 Josh Triplett
2014-10-29 19:12 ` Geert Uytterhoeven
2014-10-29 22:20 ` Josh Triplett
2014-10-30 0:35 ` Randy Dunlap
2014-10-30 2:24 ` Josh Triplett
2014-10-30 3:33 ` Martin Kelly
2014-11-03 16:46 ` Jonathan Corbet
2014-11-03 17:47 ` Joe Perches
2014-11-03 18:05 ` Josh Triplett [this message]
2014-11-03 18:39 ` Joe Perches
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=20141103180528.GA9026@jtriplet-mobl1 \
--to=josh@joshtriplett.org \
--cc=corbet@lwn.net \
--cc=joe@perches.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
all inboxes | Powered by JetHome®