-
Notifications
You must be signed in to change notification settings - Fork 9
Add abstractions and minimal implementation of rcl events #4
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
Conversation
|
@jacobperron I would like to have a feature branch in this repo (e.g. I prefer merging this yet unusable (but compiling) code there, than update this PR repeatedly. Reviewing massive PRs is painful. |
|
@ivanpauno I've given you maintainer access. You should be able to create branches now. |
|
@ivanpauno Also, you should base your changes on the |
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
9683eb1 to
c914f4f
Compare
Ups, fixed. |
Signed-off-by: Ivan Santiago Paunovic <[email protected]> Co-authored-by: Jacob Perron <[email protected]>
jacobperron
left a comment
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.
Looks reasonable to me! Some questions and minor comments below.
| * @param handle A pointer to the underlying event status. | ||
| */ | ||
| void fromRCLEvent(long handle); | ||
| } |
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.
Does it make sense to also have a "get event type" method as part of this interface?
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.
That's part of PublisherEventStatus and SubscriptionEventStatus.
Signed-off-by: Ivan Santiago Paunovic <[email protected]> Co-authored-by: Jacob Perron <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]> Co-authored-by: Jacob Perron <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]> Co-authored-by: Jacob Perron <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]> Co-authored-by: Jacob Perron <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
|
@jacobperron if you think this approach is fine, I will merge this in a feature branch and continue working on a few follow ups:
|
|
@jacobperron I have merged this into the feature branch, so I can continue with one of the other tasks listed here #4 (comment). Let me know if there are any further comments here. |
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
Signed-off-by: Ivan Santiago Paunovic <[email protected]>
This is going to be a big PR ....
I don't want to send something massive, this at least compiles though it's not yet usable.
@jacobperron I would like some early feedback, does the proposed abstractions look good?