stop enforcing c++ 11 #192
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I see that same phrasing "all over" ROS-O related PRs. That CMake setting doesn't just force C++11. It is a declaration the code in question has been tested to work and be correct for C++11 only. It's unfortunate CMake doesn't allow version ranges, but I feel it's incorrect to misrepresent what that setting is for. If you can assure me and the users here those plugins both compile and behave the same at runtime with other (ie: newer) versions of the C++ standard, we could merge. Edit: but not in a branch called |
so should there be a new |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Melodic defaults to C++14 already, ROS one requires C++ 17 due to log4cxx, so C++ 11 should not be enforced