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.

Sign up for GitHub

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

Jump to bottom

Fix #665, update pipe name documentation. #1191

Merged
merged 1 commit into from
Mar 5, 2021
Merged

Fix #665, update pipe name documentation. #1191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/cFE Application Developers Guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1439,8 +1439,8 @@ SAMPLE_AppData_t; SAMPLE_AppData;
In this example, the Developer has created a Pipe, called "SAMPLE_PIPE_1"
with a depth of 10. The Pipe name shall be at least one character and no
more than OS_MAX_API_NAME characters long. Developers should prefix their Pipe
names with the Application's abbreviated name. Although the Pipe names will
not collide with other Application Pipe names in the cFE, the
names with the Application's abbreviated name, because Pipe names will
collide with other Application Pipe names in the cFE. Also the
Developer/Operator could become confused if every Application named
their Pipe(s) "MY_PIPE". It should be noted, however, that all Pipes
for a single Application must have unique names.
Expand Down