From: "Bob Copeland" <me@bobcopeland.com>
To: "Richard Knutsson" <ricknu-0@student.ltu.se>
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 16:33:54 -0500 [thread overview]
Message-ID: <b6c5339f0802271333u3d9ad05dk26b30d59f1b41a75@mail.gmail.com> (raw)
In-Reply-To: <47C48FD8.5040205@student.ltu.se>
> > FWIW I prefer the {deleted} language. // PI = 3;
> >
> Well, actually I like it too. But I think it should be up to the
> programmer which setting to use + it seems some people have really taken
> this to heart, going from 'tab => 8 characters wide' to '8 spaces =>
> tab', obscuring tab's position as a 'logical indention'.
Well, no one's saying that you can't configure your editor any way you
want. The tabs=8 is a good cue for the 80-column rule, though.
IMO, CodingStyle used to be a good, funny read and now it's just simply
full of boring pedantic laws.
-Bob
next prev parent reply other threads:[~2008-02-27 21:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 21:47 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
2008-02-27 21:33 ` Bob Copeland [this message]
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=b6c5339f0802271333u3d9ad05dk26b30d59f1b41a75@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=bhalevy.lists@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=ricknu-0@student.ltu.se \
/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
all inboxes | Powered by JetHome®