public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Nyberg <alexn@telia.com>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>, pavel@ucw.cz
Subject: Re: Coding style: do_this(a,b) vs. do_this(a, b)
Date: Tue, 17 Aug 2004 18:07:43 +0200	[thread overview]
Message-ID: <1092758863.1948.2.camel@boxen> (raw)
In-Reply-To: <1092743463.5759.1403.camel@cube>

On Tue, 2004-08-17 at 13:51, Albert Cahalan wrote:
> > Coding style document is not consistent with
> > itself on whether there should be space after
> > ","... This makes it standartize on ", " option.
> 
> You can read it both ways, right? It's easy.
> I can't even see the difference unless I'm
> looking for it.
> 
> We don't need any more bureaucracy.
> 
> do_this(a,b);
> do_this(a, b);
> do_this (a,b);
> do_this (a, b);
> 
> I can read them all. I might notice the space in
> front of the '(', but I might not. Even putting a
> space in front of the ';' isn't unreadable.
> 
> People will pass laws until they are choked off,
> unable to move without being in violation of some
> silly little thing.

Some of us do see it and find it very annoying, I'm one of those who
very much prefer do_this(a, b) and especially when there are 
more than two parameters.

One of the reasons I do like linux is the coding standard, I find many
other projects completely unreadable.


  reply	other threads:[~2004-08-17 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 11:51 Coding style: do_this(a,b) vs. do_this(a, b) Albert Cahalan
2004-08-17 16:07 ` Alexander Nyberg [this message]
2004-08-17 16:40 ` Pavel Machek
2004-08-17 17:07   ` Albert Cahalan
2004-08-17 20:00     ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-08-17 10:38 Pavel Machek
2004-08-17 21:09 ` Fao, Sean
2004-08-17 21:14   ` Pavel Machek
2004-08-17 21:59 ` Frank van Maarseveen
2004-08-17 22:29   ` Andrew Morton

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=1092758863.1948.2.camel@boxen \
    --to=alexn@telia.com \
    --cc=albert@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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