-
Notifications
You must be signed in to change notification settings - Fork 220
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
time and timeouts have no consistent type in OSAL #571
Comments
Looks like some timeouts handle OS_PEND (-1). although inconsistent use of int32/uint32. Example code snips: osal/src/os/inc/osapi-os-core.h Lines 149 to 154 in 9407cdf
osal/src/os/inc/osapi-os-core.h Line 694 in 9407cdf
osal/src/os/inc/osapi-os-core.h Line 863 in 9407cdf
osal/src/os/inc/osapi-os-core.h Line 1020 in 9407cdf
osal/src/os/inc/osapi-os-core.h Line 1156 in 9407cdf
osal/src/os/inc/osapi-os-core.h Line 1411 in 9407cdf
|
Document change only, updates the interrupt handler section to note OSAL deprecation
Fix nasa#571, Update App Dev Guide Int Handler
In OSAL, time and timeouts are represented typically by both int32 or uint32. This convention is used in many places. It might make sense to have a consistent type for time. Perhaps even absolute and relative time. There are Wconversion issues with uses of these types.
The text was updated successfully, but these errors were encountered: