Skip to content
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

Fix #17: Update function description blocks across OSAL #21

Merged
merged 1 commit into from
Oct 1, 2019

Conversation

jphickey
Copy link
Contributor

@jphickey jphickey commented Sep 18, 2019

Describe the contribution
Fix #17

Update inline block comments in function/file headers across all of OSAL and ensure consistency with the code itself.

  • All documentation covering the specific details, inputs/outputs
    and return values should be on the function declaration, not the
    definition.

  • The definition should also contain a block comment for visual
    distinction in the source file, but should be brief and refer
    back to the prototype/declaration for detail. Any detail information
    that was indicated only with the definition is moved to the
    declaration.

  • Add doxygen tags/markup to external/public API block comments
    and expand the descriptions of these functions where needed.

  • Add block comments to the internal API prototypes, but not
    as doxygen tags/markup. Note these functions are internal use,
    not part of the public API, and are not necessarily intended
    to be stable across OSAL releases like the public API is.

  • Removed stray prototypes for functions where there was no
    actual definition/implementation.

NOTE: All changes are primarily confined to comments, except where unused/unimplemented prototypes were removed.

Testing performed
Rebuilt CFE/OSAL per default config, with unit test enabled. Confirm build as successful and unit tests execute.

Expected behavior changes
No impact to behavior

System(s) tested on:
Ubuntu 18.04 (64-bit)

Contributor Info
Joseph Hickey, Vantage Systems, Inc.

Update all block comments for OSAL functions to follow a
consistent style and ensure correctness of the descriptions.

- All documentation covering the specific details, inputs/outputs
and return values should be on the function _declaration_, not the
definition.

- The definition should also contain a block comment for visual
distinction in the source file, but should be brief and refer
back to the prototype/declaration for detail.  Any detail information
that was indicated only with the definition is moved to the
declaration.

- Add doxygen tags/markup to external/public API block comments
and expand the descriptions of these functions where needed.

- Add block comments to the internal API prototypes, but _not_
as doxygen tags/markup.  Note these functions are internal use,
not part of the public API, and are not necessarily intended
to be stable across OSAL releases like the public API is.

- Removed stray prototypes for functions where there was no
actual definition/implementation.
@skliper skliper added this to the 5.0.0 milestone Sep 19, 2019
@skliper
Copy link
Contributor

skliper commented Sep 19, 2019

Suggest adding OS_TimerSet note about cancelling with OS_TimerDelete.

@skliper skliper added the CCB:Approved Indicates code review and approval by community CCB label Oct 1, 2019
@skliper skliper changed the base branch from master to merge-20191001 October 1, 2019 19:14
@skliper skliper merged commit be7d24f into nasa:merge-20191001 Oct 1, 2019
@jphickey jphickey deleted the fix-17-function-comments branch December 3, 2020 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CCB:Approved Indicates code review and approval by community CCB
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants