From: Benny Halevy <bhalevy@panasas.com>
To: Xavier Bestel <xavier.bestel@free.fr>, DervishD <lkml@dervishd.net>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Coding Style: indenting with tabs vs. spaces
Date: Sun, 11 Nov 2007 10:57:45 +0200 [thread overview]
Message-ID: <4736C409.9040207@panasas.com> (raw)
In-Reply-To: <1194697674.6176.1.camel@bip.parateam.prv>
On Nov. 10, 2007, 14:27 +0200, Xavier Bestel <xavier.bestel@free.fr> wrote:
> Le samedi 10 novembre 2007 à 13:04 +0100, DervishD a écrit :
>> Hi Benny :)
>>
>> * Benny Halevy <bhalevy@panasas.com> dixit:
>>> I would like to hear peoples opinion about the indentation convention
>>> described below that I personally found the most practical with
>>> several different editors.
>> While I respect you opinion about tabs, I find tab indentation the most
>> evil thing ever invented. Even if done right (that is, not indenting
>> using a mixture of spaces and tabs), the only advantage is that you save
>> a few bytes.
>
> Who cares ?
> The only advantage is that people can make tabs as big (or as small) as
> they wish. Tabs become "logical indentation". So one's indentation isn't
> forced on anotherone's editor.
Right. That's exactly the point.
I find it harder to read someone else's code if (s)he uses 2 space indentation.
With tabs, when done right, I can expand to my personal preference.
>
> Xav
>
>
prev parent reply other threads:[~2007-11-11 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 10:36 Coding Style: indenting with tabs vs. spaces Benny Halevy
2007-11-08 15:58 ` Chris Snook
2007-11-12 8:17 ` Benny Halevy
2007-11-10 12:04 ` DervishD
2007-11-10 12:27 ` Xavier Bestel
2007-11-10 16:50 ` DervishD
2007-11-11 9:23 ` James Courtier-Dutton
2007-11-12 8:13 ` Benny Halevy
2007-11-12 15:38 ` J. Bruce Fields
2007-11-12 16:30 ` DervishD
2007-11-11 8:57 ` Benny Halevy [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=4736C409.9040207@panasas.com \
--to=bhalevy@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dervishd.net \
--cc=xavier.bestel@free.fr \
/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