public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tab@snarc.org (Vincent Hanquez)
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Michael S. Tsirkin" <mst@mellanox.co.il>, linux-kernel@vger.kernel.org
Subject: Re: kernel guide to space (updated)
Date: Sat, 30 Jul 2005 11:58:36 +0200	[thread overview]
Message-ID: <20050730095836.GA21671@snarc.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0507290929250.26861@yvahk01.tjqt.qr>

On Fri, Jul 29, 2005 at 09:40:14AM +0200, Jan Engelhardt wrote:
> >3i. if/else/do/while/for/switch
> >	space between if/else/do/while and following/preceeding
> >	statements/expressions, if any
> 
> Why this? if(a) {} is not any worse than if (a). I would make this an option.

please no, it's really better to have a unified CodingStyle.
and "if (" is a lot more used than "if(".

$ grep -r "if (" linux-2.6.12/* | wc -l 
288027
$ grep -r "if(" linux-2.6.12/* | wc -l 
20682


-- 
Vincent Hanquez

  parent reply	other threads:[~2005-07-30  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 14:53 kernel guide to space (updated) Michael S. Tsirkin
2005-07-28 15:52 ` linux-os (Dick Johnson)
2005-07-28 16:45   ` John W. Linville
2005-07-28 16:40 ` Dmitry Torokhov
2005-07-29  7:29   ` Jan Engelhardt
2005-07-29  7:40 ` Jan Engelhardt
2005-07-29 10:13   ` Joost Remijn
2005-07-29 17:57   ` David Weinehall
2005-07-29 19:52     ` Jan Engelhardt
2005-07-29 20:13       ` David Weinehall
2005-07-30 11:41         ` Jan Engelhardt
2005-07-30 13:38           ` David Weinehall
2005-07-30 18:32             ` Jan Engelhardt
2005-07-30  9:58   ` Vincent Hanquez [this message]
2005-08-01  2:15   ` Miles Bader

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=20050730095836.GA21671@snarc.org \
    --to=tab@snarc.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    /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