Use consistent time definition for TBL subsystem data structures #2543
Assignees
Labels
Comments
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Apr 3, 2024
Use the CFE_TIME_SysTime_t type more consistently across TBL where time is being stored. Avoid using seconds/subseconds directly. This also adds an initializer value for CFE_TIME_SysTime_t that has seconds/subseconds as zero.
2 tasks
dzbaker
added a commit
that referenced
this issue
Apr 5, 2024
Fix #2543, consistent TIME values for TBL structures
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently the TBL data structures use a mixture of TIME representations. In some cases it uses the
CFE_TIME_SysTime_tvalue, and in other cases it uses twouint32values.Describe the solution you'd like
Use the
CFE_TIME_SysTime_trepresentation of time consistently.Describe alternatives you've considered
N/A
Additional context
Consistent use of the same data type for TIME representation allows data to be exchanged more easily and simplifies the code. The
CFE_TIME_SysTime_thas getters and macros that support and simplify use of this type. These should be leveraged/used in TBL rather than repeating the logic.Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: