| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 13 Apr 2009 22:54:37 +0300 From: Matti Aarnio <matti.aarnio@...iler.org> To: Krishna Gopal <linuxkrishna@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Linux coding standards - User space 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists