Elektra  0.8.21
CODING

intensively (except for file headers).

This document provides an introduction in how the source code of libelektra is organized and how and where to add functionality.

Make sure to read DESIGN together with this document.

Folder structure

After you downloaded and unpacked Elektra you should see some folders. The most important are:

Source Code

libelektra is the ANSI/ISO C99-Core which coordinates the interactions between the user and the plugins.

The plugins have all kinds of dependencies. It is the responsibility of the plugins to find and check them using CMake. The same guidelines apply to all code in the repository including the plugins.

libloader is responsible for loading the backend modules. It works on various operating systems by using libltdl. This code is optimized for static linking and win32.

kdb is the commandline-tool to access and initialize the Elektra database.

General Guidelines

You are only allowed to break a guideline if there is a good reason to do so. When you do, document the fact as comment next to the code.

Of course, all rules of good software engineering apply: Use meaningful names and keep the software both testable and reusable.

The purpose of the guidelines is to have a consistent style, not to teach programming.

If you see code that breaks guidelines do not hesitate to fix them. At least put a TODO marker to make the places visible.

If you see inconsistency within the rules do not hesitate to talk about it with the intent to add a new rule here.

See DESIGN document too, they complement each other.

Code Comments

Code is not only for the computer, but it should be readable for humans, too. Up-to-date code comments are essential to make code understandable for others. Thus please use following techniques (in order of preference):

  1. Comment functions with /**/ and Doxygen, see below.
  2. You should also add assertions to state what should be true at a specific position in the code. Their syntax is checked and they are automatically verified at run-time. So they are not only useful for people reading the code but also for tools. Assertions in Elektra are used by:

    #include <kdbassert.h>

    ELEKTRA_ASSERT (condition, "formatted text to be printed when assert fails", ...)

    Note: Do not use assert for user-APIs, always handle arguments of user-APIs like untrusted input.

  3. If the "comment" might be useful to be printed during execution, use logging:

    #include <kdblogger.h>

    ELEKTRA_LOG ("formatted text to be printed according log filters", ...)

    Read HERE for how to enable the logger.

  4. Otherwise comment within source with // or with /**/ for multi-line comments.

Coding Style

Split up when those limits are reached. Rationale: Readability with split windows.

The reformat script can ensure most code style rules, but it is obviously not capable of ensuring everything (e.g. naming conventions). So do not give this responsibility out of hands entirely.

C Guidelines

Example: src/libs/elektra/kdb.c

C++ Guidelines

Example: src/bindings/cpp/include/kdb.hpp

Markdown Guidelines

Doxygen Guidelines

doxygen is used to document the API and to build the html and pdf output. We also support the import of Markdown pages. Doxygen 1.8.8 or later is required for this feature (Anyways you can find the API Doc online). Links between Markdown files will be converted with the Markdown Link Converter. Markdown pages are used in the pdf, therefore watch which characters you use and provide a proper encoding!

File Headers

Files should start with:

        /**
         * @file
         *
         * @brief <short statement about the content of the file>
         *
         * @copyright BSD License (see LICENSE.md or https://www.libelektra.org)
         */

Note:

The duplication of the filename, author and date is not needed, because this information is tracked using git and doc/AUTHORS.md already.