-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve consistency when working with OSAL status codes #1755
Comments
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Aug 3, 2021
Ensure a separate stack variable, always named "OsStatus", is used to hold the result of an OSAL API call. Do not use the same variable that is used to store a CFE status code.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Aug 3, 2021
Ensure a separate stack variable, always named "OsStatus", is used to hold the result of an OSAL API call. Do not use the same variable that is used to store a CFE status code.
Yes, I consider this related to #1676, as this addresses part of that one - however that previous issue was more general in nature. This issue just deals with specifically having a separate variable for OSAL status vs. CFE status. |
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Aug 4, 2021
Ensure a separate stack variable, always named "PspStatus", is used to hold the result of a PSP API call. Do not use the same variable that is used to store a CFE status code.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Aug 9, 2021
Ensure a separate stack variable, always named "OsStatus", is used to hold the result of an OSAL API call. Do not use the same variable that is used to store a CFE status code.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Aug 9, 2021
Ensure a separate stack variable, always named "PspStatus", is used to hold the result of a PSP API call. Do not use the same variable that is used to store a CFE status code.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Aug 17, 2021
Ensure a separate stack variable, always named "OsStatus", is used to hold the result of an OSAL API call. Do not use the same variable that is used to store a CFE status code.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Aug 17, 2021
Ensure a separate stack variable, always named "PspStatus", is used to hold the result of a PSP API call. Do not use the same variable that is used to store a CFE status code.
astrogeco
added a commit
that referenced
this issue
Aug 18, 2021
Fix #1755, separate variable for OSAL status
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.
Quite often in the CFE implementation, OSAL status codes are mixed with CFE status codes, often times sharing a single stack variable to hold either one, and even switching back and forth.
To improve clarity and consistency, OSAL status codes should be stored in a separate stack variable from the CFE status codes. Ideally, in the future, these should also migrate to a separate type (e.g.
osal_status_t
, as in nasa/osal#1108, orCFE_Status_t
, as in #921).Describe the solution you'd like
OsStatus
(as opposed to "Status" or "ReturnCode" etc, which are vague).Additional context
This can be considered a prerequisite to #921 (cannot introduce a unique
CFE_Status_t
type until it is no longer being used to store OSAL codes).This would be a fix for next release (not 7.0.0).
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: