From collectd Wiki
While we're very liberal when it comes to coding style, there are a few rules you ought to stick to. They're mostly obvious, but I don't write this down because I'm bored either..
Please note that these are more guidelines than a fixed set of rules. If you have a good reason for breaking one of these points, go ahead. But you may be bothered to explain why you did so.
There is one absolutely unbreakable rule though:
Programs must be written for people to read, and only incidentally for machines to execute.— Abelson / Sussman
- If you're writing a patch, please use the indentation of the surrounding code.
- If you're starting a new file, we recommend to indent with two spaces.
Function and variable names
- Names should follow the lowercase-with-underscores naming scheme, e.g.: "
temperature_current". Mixed-case names, as popular with Java developers, should not be used, i.e. don't use "
- Do not use non-ASCII characters in variable and function names.
- Names should be as long as necessary - not longer, but not shorter either. If in doubt, use the more descriptive (longer) name.
- All-capital names are reserved for, and should be used by, defines, macros and enum-members.
- If several variables or functions with similar meaning exist, such as minimum, average and maximum temperature, the common part should be in front, e.g. "
temp_min" and so on.
- Non-static functions must be declared in a header file that has the same base name as the
.cfile defining the function.
staticfunctions should not have a forward declaration.
- All functions within a plugin should be declared
static. The obvious exception is the "
module_register" function (see plugin architecture).
- The behavior of a plugin should not depend on compile time settings. If this cannot be guaranteed, for example because the library a plugin uses must be a certain version for an optional feature, this has to be documented in the collectd.conf(5) manual page.
- Only reentrant- and thread-safe functions and libraries may be used.
Fixed size buffers
- The functions
sprintfmust not be used.
- Instead of
ssnprintf. These functions assure a null byte at the end of the buffer.
- Only explicitly give the size of the buffer when declaring it. Use the
sizeofoperator or the
STATIC_ARRAY_SIZEmacro after that. Please don't hide the actual size of the buffer in some define.
- Please do not mix variable declarations and code. Declare all variables at the beginning of a block.
- Please do not use C++-style comments. Use
/* … */instead.
- Please do not use flexible array members (FAM).
- Please use the integer types found in
<stdint.h>if you need a fixed size integer, e.g. for parsing binary network packets and the like. If you need to print such a variable, please use the printing macros provided by
- Feel free to use the
_Booltype. Assign only the numeric values
0(false) to these variables (i.e. don't use any defines, such as
- Do not compare
size_twithout a cast. Those two types cannot be cast to one another automatically on many platforms.
- Use the
%zuformat when printing
License information and copyright notice
- All source files must begin with a short license note including a copyright statement. We recommended to copy and adapt the comment from another file.
- Any GPLv2 compatible, OSI approved, free / open-source license is acceptable.
- For new files, we recommend to use the MIT license.
- GPL: Please note that most files in collectd are licensed under the terms of the GPLv2 only, not the otherwise widely used "GPLv2 or later" schema. If you want to permit the use of your code under the terms of the GPLv3, please adapt the header.
- Please spell your name in the copyright notice as it should be written according to your native language. If you need non-ASCII characters for this, make sure the file is encoded using the UTF-8 character set.