mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Krishna Gopal <linuxkrishna@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux coding standards - User space
Date: Mon, 13 Apr 2009 22:54:37 +0300	[thread overview]
Message-ID: <20090413195437.GM28512@mea-ext.zmailer.org> (raw)
In-Reply-To: <68f510a70904131210s38188475ie878f2775d92cab6@mail.gmail.com>

On Mon, Apr 13, 2009 at 02:10:48PM -0500, Krishna Gopal wrote:
> 
> Are there any coding guidelines for Linux User space programming ?
> 

No.  The problem space is way too large.

Understand the problem being solved, use tools you know how, learn better
ones when necessary, try using existing tools.  Do not recreate the wheel
(write new program code) without good reason. This results often in amazing
number of libraries needed for even _simple_ programs to work, which itself
has become a problem.

Trade that code self-writing/copying against the number of needed libraries,
and their source licenses.   Self-written and copied codes are prone to
errors, which does not mean that popular libraries are immuned to errors
either, but getting library fixed does fix all programs using that library.

I am hyper-conservative myself to add any new library into use.  The less
libraries the code uses, the better is its portability to new platforms.
I myself do not consider locking application code to only Linux being 
acceptable, it is more sign of its coder having too narrow thinking.

Portability among different flavours of UNIX may need surprising things,
and $BigMoney applications get to run in POSIX systems that often are not
Linux.  Sometimes even on Windows.

> BR,
> Krishna

BR, Matti

      reply	other threads:[~2009-04-13 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 19:10 Krishna Gopal
2009-04-13 19:54 ` Matti Aarnio [this message]

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=20090413195437.GM28512@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxkrishna@gmail.com \
    /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

all inboxes | Powered by JetHome®