-
Notifications
You must be signed in to change notification settings - Fork 70
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
Implementation for Deadline, Liveliness, and Lifespan QoS #167
Conversation
* \return `RMW_RET_OK` if successful, or | ||
* \return `RMW_RET_BAD_ALLOC` if memory allocation failed, or | ||
* \return `RMW_RET_ERROR` if an unexpected error occurs. | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The doc block style we use is:
/// Brief description, which is concise and a single line only.
/**
* A longer description.
*
* Perhaps with detailed explanation of the behavior of the function.
* But always, one sentence per line.
* Another sentence is here.
*
* \param[in] input An input argument.
* \param[out] output An output argument.
* \return `RMW_RET_OK` if successful, or
* \return `RMW_RET_BAD_ALLOC` if memory allocation failed, or
* \return `RMW_RET_ERROR` if an unexpected error occurs.
*/
...
Note the differences, like /**
at the start, the brief being on it's own ///
line, the param's having in/out designations, etc.
Also the taken
argument is not documented.
@@ -239,6 +299,154 @@ typedef enum RMW_PUBLIC_TYPE | |||
RMW_LOG_SEVERITY_FATAL = RCUTILS_LOG_SEVERITY_FATAL | |||
} rmw_log_severity_t; | |||
|
|||
/// Defined in the DDS SSpec 15-04-10 section 2.2.4.1 Communication Status |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't seem like a brief description for the struct, so either reformat it so that it is, or consider just using //
.
typedef struct RMW_LIVELINESS_CHANGED_STATUS | ||
{ | ||
/** | ||
* The total number of currently active DataWriters that write the Topic read by the DataReader. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rmw documentation should not speak about DDS concepts like DataWriter, etc.. It needs to be in generic terms that are not tied to a specific rmw implementation.
Closing this pull request in favor of #171. |
Implementation for Deadline, Liveliness, and Lifespan QoS. The design is at ros2/design#212
This is currently a work in progress.