From: Richard Knutsson <ricknu-0@student.ltu.se>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
khc@pm.waw.pl, bhalevy.lists@gmail.com, jengelh@computergmbh.de,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] CodeStyle: Use spaces when aligning/decorating
Date: Wed, 27 Feb 2008 22:02:39 +0100 [thread overview]
Message-ID: <47C5CFEF.8020402@student.ltu.se> (raw)
In-Reply-To: <47C4AB5D.3000900@panasas.com>
Benny Halevy wrote:
>
> How about this:
>
> -Tabs are 8 characters, and thus indentations are also 8 characters.
> -There are heretic movements that try to make indentations 4 (or even 2!)
> -characters deep, and that is akin to trying to define the value of PI to
> -be 3.
> +Tabs are used for logical indentation, e.g., code is indented with
> +a number of tabs equal to its nesting level. From there on,
> +use space characters for decorative indentation. This method
> +is agnostic to the editor's tab-expansion settings.
> +That said, expanding tabs to a small number of spaces (4, or even 2!) encourages
> +excessive nesting and resulting over-complexity; that is akin to trying to define
> +the value of PI to be 3. Therefore, tabs are always assumed to be 8 characters-wide.
>
>
Not sure about the PI-reference in that context, but the rest IMO looks
good.
next prev parent reply other threads:[~2008-02-27 21:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 21:47 [RFC] CodeStyle: Use spaces when aligning/decorating ricknu-0
2008-02-26 21:54 ` Randy Dunlap
2008-02-26 22:16 ` Richard Knutsson
2008-02-27 0:14 ` Benny Halevy
2008-02-27 21:02 ` Richard Knutsson [this message]
2008-02-27 21:33 ` Bob Copeland
2008-02-27 21:47 ` Richard Knutsson
2008-02-26 22:59 ` [PATCH] CodingStyle: multiple updates Jan Engelhardt
2008-02-26 23:40 ` Guennadi Liakhovetski
2008-02-26 23:51 ` Krzysztof Halasa
2008-02-27 0:02 ` Jan Engelhardt
2008-02-27 0:16 ` Guennadi Liakhovetski
2008-02-27 0:42 ` Stefan Richter
2008-02-27 0:57 ` SL Baur
2008-02-27 5:34 ` Randy Dunlap
2008-02-27 21:33 ` SL Baur
2008-02-27 22:02 ` Richard Knutsson
2008-02-27 23:53 ` Krzysztof Halasa
2008-02-28 0:11 ` SL Baur
2008-02-28 0:18 ` Jan Engelhardt
2008-02-28 20:09 ` Richard Knutsson
2008-02-29 22:34 ` Krzysztof Halasa
2008-03-03 16:17 ` Benny Halevy
2008-03-03 21:08 ` Krzysztof Halasa
2008-03-04 10:04 ` Benny Halevy
2008-02-28 21:20 ` Alexey Dobriyan
2008-02-27 9:27 ` Bernd Petrovitsch
2008-02-27 10:02 ` Guennadi Liakhovetski
2008-02-27 10:17 ` Bernd Petrovitsch
2008-02-27 21:46 ` SL Baur
2008-02-27 0:39 ` Stefan Richter
2008-02-27 21:41 ` Richard Knutsson
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=47C5CFEF.8020402@student.ltu.se \
--to=ricknu-0@student.ltu.se \
--cc=bhalevy.lists@gmail.com \
--cc=bhalevy@panasas.com \
--cc=jengelh@computergmbh.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.