From: "Robert P. J. Day" <rpjday@mindspring.com>
To: "Joel M. Pareja" <jpareja@ntsp.nec.co.jp>
Cc: C programming list <linux-c-programming@vger.kernel.org>
Subject: Re: C coding convention
Date: Thu, 15 Dec 2005 21:16:44 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.63.0512152115310.26086@localhost.localdomain> (raw)
In-Reply-To: <1134699163.5461.19.camel@silver.hq.ntsp.nec.co.jp>
On Fri, 16 Dec 2005, Joel M. Pareja wrote:
> 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;
> }
> }
>
it's a bad idea since it just wastes screen space -- chewing up an
entire line for a single brace. bad boss. no biscuit.
rday
next prev parent reply other threads:[~2005-12-16 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 2:12 C coding convention Joel M. Pareja
2005-12-16 2:16 ` Robert P. J. Day [this message]
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=Pine.LNX.4.63.0512152115310.26086@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=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).