unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: "Notmuch Mail" <notmuch@notmuchmail.org>
Subject: Code Style Bikeshed 1/n: Break before Brace or Brace before Break? 
Date: Sun, 18 Dec 2011 08:04:32 -0400	[thread overview]
Message-ID: <87vcpeaxwv.fsf@zancas.localnet> (raw)


In id:"1324135695-15487-1-git-send-email-david@tethera.net" we started
discussing the use of uncrustify (or some equivalent tool) to enforce
code style. In order for this to work, we would need to be a bit more
rigid about style.

So my sunday morning bikeshed-bait is do we want 

if (...) {
}

or 

if (...) 
{
}

(and similarly for 'switch', 'for', 'while')

If I look at a small sample of Carl's original code it seems like the
former is more typical. But I might be biased because that is what I
prefer.

d

             reply	other threads:[~2011-12-18 12:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-18 12:04 David Bremner [this message]
2011-12-18 15:50 ` Code Style Bikeshed 1/n: Break before Brace or Brace before Break? Dmitry Kurochkin
2011-12-18 16:12   ` Tomi Ollila
2011-12-18 16:18     ` Dmitry Kurochkin
2012-01-12 17:18       ` Pieter Praet
2011-12-18 17:13     ` Austin Clements

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vcpeaxwv.fsf@zancas.localnet \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.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. 
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).