From: "Joel M. Pareja" <jpareja@ntsp.nec.co.jp>
To: C programming list <linux-c-programming@vger.kernel.org>
Subject: C coding convention
Date: Fri, 16 Dec 2005 10:12:43 +0800 [thread overview]
Message-ID: <1134699163.5461.19.camel@silver.hq.ntsp.nec.co.jp> (raw)
Hi!
I just would like to hear ideas about a convention that my boss is
insisting on being implemented which I personally disagree.
Putting opening/closing brackets for case statements:
switch (type)
{
case 1:
=> {
/* do something */
break;
=> }
....
default:
{
/* do something */
break;
}
}
*I am aware that this is just a very small thing to argue. :-)
If you agree with my boss, could you point to me open source projects
that use this convention.
Thanks.
next reply other threads:[~2005-12-16 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 2:12 Joel M. Pareja [this message]
2005-12-16 2:16 ` C coding convention Robert P. J. Day
2005-12-16 10:59 ` Glynn 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1134699163.5461.19.camel@silver.hq.ntsp.nec.co.jp \
--to=jpareja@ntsp.nec.co.jp \
--cc=linux-c-programming@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 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 NNTP newsgroup(s).