From: Joe Perches <joe@perches.com>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] CodingStyle: remove what nowadays might be considered polemic
Date: Sun, 21 Dec 2014 09:09:52 -0800 [thread overview]
Message-ID: <1419181792.4200.2.camel@perches.com> (raw)
In-Reply-To: <54969F9A.80301@ahsoftware.de>
On Sun, 2014-12-21 at 11:23 +0100, Alexander Holler wrote:
> Am 19.12.2014 um 14:36 schrieb Alexander Holler:
> > 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).
checkpatch already does that looking for 6+ leading
tabs then any statement that increases indentation.
> I've heared that wrong argument that a maximum line length
> of 80 chars helps in regard to keep the levels of intendation low once
> too often.
I believe that argument correct.
helps is not a mandate.
The idea is that code that start far from the left
(for some definition of far) is a signal that code
could be refactored into more discrete chunks.
Without a limit to line length, more code would
likely not have been as disaggregated as today.
next prev parent reply other threads:[~2014-12-21 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 13:36 [RFC PATCH] CodingStyle: remove what nowadays might be considered polemic Alexander Holler
2014-12-21 10:23 ` Alexander Holler
2014-12-21 10:52 ` Alexander Holler
2014-12-21 17:09 ` Joe Perches [this message]
2014-12-22 11:51 ` Alexander Holler
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=1419181792.4200.2.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=holler@ahsoftware.de \
--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