You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The CFE_ES_ResourceId_t type is currently defined by ES, but in issue #985 and PR #1092 this was extended to be used by SB. There is also a potential to use it for TBL handles as well.
There is also some choice here - in that the CFE_ES_ResourceID_t type can be a simple typedef to uint32 for compatibility, or a type-safe wrapper to make sure it doesn't get mixed.
Describe the solution you'd like
Put the type definition and associated access functions/macros/constants into a separate CFE module, like msg and sbr are currently done. This gets it out from being an "ES" type, extending it apply to all of CFE core and possibly also apps.
Additional context
This also can incorporate a solution for #913 - each app may specialize the generic type with its own typedef.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Move all functions, macros, types, and other definitions
related to resource IDs and generic resource management into
a separate module, like CFE MSG and SBR, etc.
Notably this allows a mission to elect "strict" implementations
of these objects, where every ID type is unique, and assigning
between them (or uint32) results in a compiler error.
Move all functions, macros, types, and other definitions
related to resource IDs and generic resource management into
a separate module, like CFE MSG and SBR, etc.
Notably this allows a mission to elect "strict" implementations
of these objects, where every ID type is unique, and assigning
between them (or uint32) results in a compiler error.
Is your feature request related to a problem? Please describe.
The
CFE_ES_ResourceId_t
type is currently defined by ES, but in issue #985 and PR #1092 this was extended to be used by SB. There is also a potential to use it for TBL handles as well.There is also some choice here - in that the
CFE_ES_ResourceID_t
type can be a simple typedef touint32
for compatibility, or a type-safe wrapper to make sure it doesn't get mixed.Describe the solution you'd like
Put the type definition and associated access functions/macros/constants into a separate CFE module, like
msg
andsbr
are currently done. This gets it out from being an "ES" type, extending it apply to all of CFE core and possibly also apps.Additional context
This also can incorporate a solution for #913 - each app may specialize the generic type with its own typedef.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: