Collect related headers in single task specific headers #148

Open
opened 2020-07-21 12:08:15 +02:00 by mohr · 2 comments
Owner

Create headers which include common other headers for a common task, ie create datapool/datapool.h which includes all the headers usually needed if you use the datapool.

This would clean up the include lists.

Create headers which include common other headers for a common task, ie create datapool/datapool.h which includes all the headers usually needed if you use the datapool. This would clean up the include lists.
gaisser changed title from Collect related headers in single trask specific headers to Collect related headers in single task specific headers 2020-10-27 15:08:08 +01:00
gaisser added the
feature
label 2020-10-27 15:08:15 +01:00
Owner

I implemented this for the local data pools.

I implemented this for the local data pools.
Owner

This is being extended as part of #445 . Following files have been added so far

  • fsfw/action.h
  • fsfw/health.h
  • fsfw/datapoollocal.h
  • fsfw/housekeeping.h
  • fsfw/objectmanager.h
  • fsfw/serialize.h
  • fsfw/serviceinterface.h

There is still the architectural question whether these header files are in a separate inc folder our in src. The src folder still needs to be included because the ability to include single files is still required for internal and external purposes (e.g. including containers) so I see no issue putting it into src

This is being extended as part of #445 . Following files have been added so far - `fsfw/action.h` - `fsfw/health.h` - `fsfw/datapoollocal.h` - `fsfw/housekeeping.h` - `fsfw/objectmanager.h` - `fsfw/serialize.h` - `fsfw/serviceinterface.h` There is still the architectural question whether these header files are in a separate `inc` folder our in `src`. The `src` folder still needs to be included because the ability to include single files is still required for internal and external purposes (e.g. including containers) so I see no issue putting it into `src`
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fsfw/fsfw#148
No description provided.