Skip to content

Add F Prime terminology translation guide #3260

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

Merged
merged 4 commits into from
Feb 27, 2025
Merged

Conversation

matt392code
Copy link
Contributor

"Resolves #1251 - Creates documentation to translate software engineering concepts to F´ nomenclature"
LeStarch on Feb 13, 2025
@matt392code these tables you posted are exactly what we need for this issue. Do you want to pull those tables into a PR? Create:
docs/user-guide/framework/fprime-translations.md
Add all of the tables you put at the top (everything up to "Example Translations"). I will need to go through and edit some of the data, but want to let you get credit for the initial work.

Related Issue(s) #1251
Has Unit Tests (y/n) Not Applicable - tech documentation only
Documentation Included (y/n) y

Change Description

Adds a new documentation file that translates common software engineering concepts to F´ terminology. The guide includes mappings for:

  • Data Structures & Containers
  • Communication & Synchronization
  • Memory Management
  • System Architecture
  • Error Handling
  • Testing
  • Common Design Patterns

Rationale

This documentation helps developers transition to F´ by providing clear mappings between familiar software concepts and their F´ equivalents, as requested in issue #1251.

Testing/Review Recommendations

Please review the terminology mappings for accuracy and completeness. The documentation is based on the tables previously posted in issue #1251.

Future Work

  • Additional examples could be added after initial review
  • Terminology could be expanded based on community feedback

@LeStarch
Copy link
Collaborator

@thomas-bc sorry about the miss-communication. I specifically asked for this PR as-is extracted from the referenced issue. It was my intent to review the content here and remove the tool-artifacts.

I have done that now. Would you take a look now that I've cleaned it up? This was done to ensure @matt392code got credit for the original contribution.

Copy link
Collaborator

@thomas-bc thomas-bc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ! This should likely be added to mkdocs.yml so it can be found on the website

Apologies for the miscommunication

@matt392code
Copy link
Contributor Author

matt392code commented Feb 25, 2025 via email

matt392code and others added 2 commits February 26, 2025 10:11
LeStarch on Feb 13, 2025
CollaboratorAuthor
@matt392code these tables you posted are exactly what we need for this issue. Do you want to pull those tables into a PR?
Create:
docs/user-guide/framework/fprime-translations.md
Add all of the tables you put at the top (everything up to "Example Translations").
I will need to go through and edit some of the data, but want to let you get credit for the initial work.
@LeStarch LeStarch merged commit f44260d into nasa:devel Feb 27, 2025
3 checks passed
@LeStarch
Copy link
Collaborator

Nice work everyone!

@matt392code
Copy link
Contributor Author

matt392code commented Feb 28, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

F´ Terminology Documentation
3 participants