From: Tim Hockin <thockin@hockin.org>
To: krishna <krishna.c@globaledgesoft.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Con Kolivas <lkml@kolivas.org>
Subject: Re: How to write elegant C coding
Date: Tue, 4 Jan 2005 19:55:20 -0800 [thread overview]
Message-ID: <20050105035520.GA13645@hockin.org> (raw)
In-Reply-To: <41DB6248.2030003@globaledgesoft.com>
On Wed, Jan 05, 2005 at 09:13:04AM +0530, krishna wrote:
>
> What I mean is both elegant and _efficient_ best practices in C coding.
practice.
> Con Kolivas wrote:
>
> >krishna wrote:
> >
> >>Hi All,
> >> Can any one tell me sources to refer to write elegant C coding/
> >>best practices in C coding.
> >
> >
> >Check the kernel sources under Documentation/CodingStyle
> >
> >Cheers,
> >Con
> >
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Tim Hockin
thockin@hockin.org
Soon anyone who's not on the World Wide Web will qualify for a government
subsidy for the home-pageless.
next prev parent reply other threads:[~2005-01-05 3:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 3:26 How to write elegant C coding krishna
2005-01-05 3:42 ` Con Kolivas
2005-01-05 3:43 ` krishna
2005-01-05 3:55 ` Tim Hockin [this message]
2005-01-05 4:11 ` Alan Cox
2005-01-05 15:11 ` Horst von Brand
-- strict thread matches above, loose matches on Subject: below --
2005-01-05 6:44 krishna
2005-01-05 7:49 ` Coywolf Qi Hunt
2005-01-05 8:14 ` Al Viro
2005-01-06 15:17 krishna
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=20050105035520.GA13645@hockin.org \
--to=thockin@hockin.org \
--cc=krishna.c@globaledgesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@kolivas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.