eive/fsfw
eive
/
fsfw
forked from fsfw/fsfw
14
1
Fork 0
Code Issues Pull Requests Releases 1 Wiki Activity

doc corrections

This commit is contained in:
Robin Müller 2022-09-15 13:51:59 +02:00
parent 1a833e2d45
commit 423a9540ed
No known key found for this signature in database
GPG Key ID: 11D4952C8CCEF814
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/README-highlevel.md
View File

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