All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herman Oosthuysen <Herman@WirelessNetworksInc.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: Emiliano Gabrielli <emiliano.gabrielli@roma2.infn.it>,
	linux-kernel@vger.kernel.org
Subject: Re: Indention - why spaces?
Date: Mon, 30 Dec 2002 12:30:57 -0700	[thread overview]
Message-ID: <3E109EF1.5040901@WirelessNetworksInc.com> (raw)
In-Reply-To: <20021230190034.GG3143@conectiva.com.br>

This problem is as old as the typewriter itself.  The trouble is that a 
Tab character doesn't have a fixed size - some set it to 3 characters 
wide, some to 4 some to 8, or whatever.

The 'indent' program was written a couple of decades ago, to pretty 
print C code.  It has a 'GNU' standard, but I'm not aware of a 'Linux' 
standard.  Anyhoo, the only way to prevent indentation wars is to use 
spaces, not tabs and to set 'diff' to ignore white space when comparing 
files...

Arnaldo Carvalho de Melo wrote:
> Em Mon, Dec 30, 2002 at 07:53:22PM +0100, Emiliano Gabrielli escreveu:
> 
>><quote who="Dave Jones">
>>
>>>On Mon, Dec 30, 2002 at 12:49:33PM +0000, John Bradford wrote:
>>> > > Well, I disagree: http://www.wiggy.net/rants/tabsvsspaces.xhtml
>>> > In my opinion, indentation in any form is irritating.
>>>
>>>The devfs source code is --> that way.
>>>
>>
>>IMHO and in my personal projects I use the following indenting rules:
>>
>>1) use TABs for _indentation_
>>2) use SPACEs for aligning
>>
>>here is an exaple:
>>
>><tab><tab>if (cond) {
>><tab><tab><tab>dosometing;
>><tab><tab><tab>printf("This is foo: '%s', and this bar: '%d'",
>><tab><tab><tab>       foo, bar);
>>
>>where tabs are explicitated, while spaces not.
>>
>>
>>I think this way combines both tab and spaces advantages, allowing each coder
>>to have its own indentation width, but NEVER destroing the aspect of the code.
>>
>>This is only my opinion :-P
> 
> 
> I second that.
> 
> - Arnaldo
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 

------------------------------------------------------------------------
Herman Oosthuysen
B.Eng.(E), Member of IEEE
Wireless Networks Inc.
http://www.WirelessNetworksInc.com
E-mail: Herman@WirelessNetworksInc.com
Phone: 1.403.569-5687, Fax: 1.403.235-3965
------------------------------------------------------------------------



  reply	other threads:[~2002-12-30 19:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.f9m4suv.e6ubgf@ifi.uio.no>
2002-12-30  3:33 ` Indention - why spaces? Russ Allbery
2002-12-30  3:43   ` Larry McVoy
2002-12-30  3:47     ` john slee
2002-12-30  4:26     ` Russ Allbery
2002-12-30 23:20     ` Mark Mielke
2002-12-30 12:28   ` Wichert Akkerman
2002-12-30 12:49     ` John Bradford
2002-12-30 12:57       ` Wichert Akkerman
2002-12-30 13:12       ` Rik van Riel
2002-12-30 13:16       ` Russell King
2002-12-30 13:17       ` Dave Jones
2002-12-30 18:53         ` Emiliano Gabrielli
2002-12-30 19:00           ` Arnaldo Carvalho de Melo
2002-12-30 19:30             ` Herman Oosthuysen [this message]
2002-12-30  9:42               ` Zac Hansen
2002-12-30 20:43               ` Felix Domke
2002-12-30 23:26                 ` Mark Mielke
2002-12-31  1:02                   ` Wichert Akkerman
2002-12-30 23:55                 ` Herman Oosthuysen
2002-12-31  2:20               ` Anthony J. Breeds-Taurima
2002-12-31  9:47                 ` Christoph Hellwig
     [not found]         ` <mailman.1041274740.23755.linux-kernel2news@redhat.com>
2002-12-31  5:28           ` Pete Zaitcev
2002-12-31  6:04             ` Larry McVoy
2002-12-30 16:12     ` Larry McVoy
2002-12-31 22:43 Heater, Daniel (IndSys, GEFanuc, VMIC)
  -- strict thread matches above, loose matches on Subject: below --
2002-12-31 17:21 Roberto Peon
2002-12-30  2:29 Felix Domke
2002-12-30 11:28 ` Christoph Hellwig
2002-12-31  8:55   ` Tomas Szepe

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=3E109EF1.5040901@WirelessNetworksInc.com \
    --to=herman@wirelessnetworksinc.com \
    --cc=acme@conectiva.com.br \
    --cc=emiliano.gabrielli@roma2.infn.it \
    --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 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.