-
Notifications
You must be signed in to change notification settings - Fork 20
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
Implement header file naming convention for SC #112
Comments
jphickey
added a commit
to jphickey/SC
that referenced
this issue
Oct 9, 2023
Follow the header file convention documented in CFE
jphickey
added a commit
to jphickey/SC
that referenced
this issue
Oct 12, 2023
Follow the header file convention documented in CFE
jphickey
added a commit
to jphickey/SC
that referenced
this issue
Oct 12, 2023
Follow the header file convention documented in CFE
jphickey
added a commit
to jphickey/SC
that referenced
this issue
Oct 12, 2023
Follow the header file convention documented in CFE
jphickey
added a commit
to jphickey/SC
that referenced
this issue
Oct 12, 2023
Follow the header file convention documented in CFE
jphickey
added a commit
to jphickey/SC
that referenced
this issue
Oct 12, 2023
Follow the header file convention documented in CFE
jphickey
added a commit
to jphickey/SC
that referenced
this issue
Oct 12, 2023
Follow the header file convention documented in CFE
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist (Please check before submitting)
Is your feature request related to a problem? Please describe.
A convention/pattern for header file content was documented in nasa/cFE#2306, and is being further refined in nasa/cFE#2451
Describe the solution you'd like
SC should follow the documented naming convention.
Additional context
All components should be consistent
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: