fsfw/fsfw
fsfw
/
fsfw
10
3
Fork 6
Code Issues 31 Pull Requests 4 Releases 10 Wiki Activity

v6.0.0 #729

Merged
mohr merged 668 commits from development into master 2023-02-23 13:42:49 +01:00
Conversation 0 Commits 668 Files Changed 816 +6 -8
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 131e3ff1e3 - Show all commits

14
docs/README-highlevel.md
View File

@ -4,14 +4,12 @@ High-level overview
# Structure
The general structure is driven by the usage of interfaces provided by objects.
The FSFW uses C++17 as baseline. Most modern compilers like GCC should have support for this
standard, even for micocontrollers.
The FSFW uses dynamic allocation during the initialization but provides static containers during
runtime.This simplifies the instantiation of objects and allows the usage of some standard
containers. Dynamic Allocation after initialization is discouraged and different solutions are
provided in the FSFW to achieve that. The fsfw uses run-time type information but will not throw
exceptions.
The FSFW uses C++11 as baseline. The intention behind this is that this C++ Standard should be
widely available, even with older compilers.
The FSFW uses dynamic allocation during the initialization but provides static containers during runtime.
This simplifies the instantiation of objects and allows the usage of some standard containers.
Dynamic Allocation after initialization is discouraged and different solutions are provided in the
FSFW to achieve that. The fsfw uses run-time type information but exceptions are not allowed.
# Failure Handling