-
Notifications
You must be signed in to change notification settings - Fork 128
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
Use c++11 and remove boost dependency #62
Comments
@wjwwood any thoughts? |
We don't have a plan for migrating to C++11 types within ROS 1, but adding a typedef which doesn't already exist which points to the C++11 types is probably a good strategy. I'm not sure what the sticking points will be in the transition, but if I see a concrete proposal (pull request) I can give feedback on what might be affected based on that. We already guarantee that ROS 1 will compile when Quickly looking at
Which is probably replaced by It also uses
https://github.com/ros/urdfdom_headers/blob/56471a55d85e1be27a91a5f2f72b001d92cddb15/urdf_sensor/include/urdf_sensor/sensor.h#L157 (and others) And |
my concern is that there is a lot of code that depends on these types, so I am not too inclined to change this. What do you think of forking to an urdfdom2 that uses c++11 and avoids boost? |
Adding c++11 is a huge change, so I had assumed that would involve a major version bump. I had imagined that it could just live in a new branch. Do we need to fork and make a package with a new name (like |
Bump my previous comment: can we make breaking changes in a new release branch (bumping the major version), or does it need to be in a new repository? |
I'd say do it as a branch, but @isucan should make the call. |
Please do this in a new branch, no need for a new repo. |
I just made a pull request to urdfdom_headers to create typedefs for smart pointers. It should preserve backwards compatibility but make it easier to migrate away from boost. |
boost is gone! |
Are there any plans to make a version of urdfdom that uses c++11 and replaces
boost::*_ptr
withstd::*_ptr
? One semi-migration strategy could be to start using typedefs:and then in the next major version of urdfdom switch them over to
std::
instead ofboost::
Then anyone who wants their code to support both versions could use the typedefs? I'm sure there's big holes in this strategy (such as
boost::*_pointer_cast
vsstd::*_pointer_cast
), but you've got to start somewhere.The text was updated successfully, but these errors were encountered: