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

Revert "doc corrections"
All checks were successful
fsfw/fsfw/pipeline/head This commit looks good
Details

Browse Source 
This reverts commit 423a9540ed.
This commit is contained in:
Robin Müller 2022-09-15 13:52:28 +02:00
parent 423a9540ed
commit 131e3ff1e3
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/README-highlevel.md
View File

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