DEVELOPERS.md

Development guide

Note that any command described here assumes that your PWD is trabalho-pratico.

Extra dependencies

Some programs, not listed in README.md, are not required to build the project per se, but are very useful for developing it:

• clang-format (code formatting);
• Doxygen (documentation generation);
• TeX Live (pdflatex in specific, for report generation);
• Valgrind (profiling and leak checking);
• Kcachegrind (seeing profiling results);
• ShellCheck (static analysis of scripts);
• act (running GitHub actions locally).

Other build types

Builds for debugging and profiling are available, by setting the environment variables DEBUG and PROFILE to 1, respectively.

$ DEBUG=1 make
$ PROFILE=1 make

Don't forget to run make clean between different build types.

Documentation generation

Doxygen documentation can be generated by running:

$ make docs

HTML documentation should be outputted to docs/html/index.html.

Developer-written reports can be compiled with:

$ make report

Profiling

The code can be profiled using callgrind + kcachegrind, both automatically started by the callgrind.sh script:

$ ./scripts/callgrind.sh

A PROFILE build is recommended.

Checking for memory leaks

Please use our wrapper around valgrind:

$ ./scripts/leakcheck.sh

A DEBUG build is recommended.

Code style

Formatting

The format.sh script will attempt to format the whole project to a temporary directory (using clang-format), and then compare the results with your original source files. You can choose whether or not you want to keep those changes (you may want to manually disable formatting for a snippet of code, for example). Keep in mind that there's a CI action that requires formatting to be correct, so you can't just leave your source code unformatted.

$ ./scripts/format.sh

As any other formatter configuration, there are many tunable parameters. For your code editor, set the column limit to 100, the tab size to 4, with tab expansion on, and let clang-format handle the rest.

Naming

Methods, variables and types should be named in snake_case. In specific, type names should end in _t, such as, for example, deque_t. Also, methods related to a type must start with that type's name (e.g.: deque_push_front).

Other

/* ANSI C style */ comments are preferred. Also, headers from the project must be included in double quotes (#include "internal_header.h").

Other scripts

• todo.sh - looks for the TODO string in all C sources and headers.
• contributors.sh - counts how many lines of code each contributor committed. This replaces my need for GitHub Pro, needed to perform this action on private repos.

GitHub Actions

The CI pipeline is very simple: it checks if the code is correctly formatted, and it builds the project. shellcheck verification of scripts is also present. All of these can be run locally, without any containerization.

However, you may want to run the CI actions in a environment similar to the one in a GitHub runner, for example, to use the same version of clang-format. Our actions are compatible with act. However, you are sure to expect a longer running time, as clang-format, not available on act's default Ubuntu image, needs to be installed.