From: Alexander Holler <holler@ahsoftware.de>
To: Joe Perches <joe@perches.com>
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: Mon, 22 Dec 2014 12:51:11 +0100 [thread overview]
Message-ID: <549805AF.2080604@ahsoftware.de> (raw)
In-Reply-To: <1419181792.4200.2.camel@perches.com>
Am 21.12.2014 um 18:09 schrieb Joe Perches:
> 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.
Oh, nice. I didn't know that.
>> 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.
I think people just make variable and function names even more cryptic
(shorter) in order to let them fit into the remaining free space. That
seems to be easier for most than to refactor their code.
Regards,
Alexander Holler
prev parent reply other threads:[~2014-12-22 11:51 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
2014-12-22 11:51 ` Alexander Holler [this message]
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=549805AF.2080604@ahsoftware.de \
--to=holler@ahsoftware.de \
--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