data-structures-for-embedded-systems | data structures that use static memory allocation

data-structures-for-embedded-systems is a C library typically used in Framework applications. data-structures-for-embedded-systems has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

This repository contains a code-base that I find useful for isolating the embedded applications I write from the characteristics that vary between hardware systems and microcontroller architectures. Each module is coded using dependency-injection, which allows compiling, testing, and integrating each module independently; making it more portable and modular. The idea is basically to write the modules by programming towards a generic interface whose concrete implementation can vary from one application (or running environment) to another. Most modules implement a base data-structure that carries with the information of the module dependencies and its attributes. For example, the module MyModule defines the data structure MyModule_t. Also, inside MyModule_t, the user must specify a concrete implementation of the "dependency Z" for the module to be integrated into an application. In this way, the user can separate the dependency implementation, the module itself, and the application so that they can be maintained/changed independently. In each module, the header MyMoudule.h contains the public declarations, while the behavioral implementation is inside the correspondent source file MyModule.c. Often, the source file contains only standard-C-library functions and calls to the dependencies (using the generic interfaces available in the module data-structure definition). Since this code is oriented towards embedded applications, I recommend to initialize the module data-structures statically (avoiding dynamic memory allocation). The code-base includes modules that are common to embedded applications such as general-purpose-IO, counters, queues, etc. Please feel free to comment, ask questions, or give me advice on how to improve the code.