Use c++11 and remove boost dependency about urdfdom

[scpeters]

boost is gone!

[scpeters]

@wjwwood any thoughts?

[wjwwood]

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 -std=c++11 is passed to the compiler, so we only have to consider the upgrade with respect to types that have changed. We probably won't be able to drop the boost dependency anytime soon. Because we use boost::filesystem and boost::program_options and a few other things which have no C++11 equivalent.

Quickly looking at urdfdom it uses boost::lexical_cast:

urdfdom/urdf_parser/src/urdf_model_state.cpp

Line 41 in ccc7d2f

#include <boost/lexical_cast.hpp>

Which is probably replaced by std::to_string.

It also uses shared_ptr in the public API:

urdfdom/urdf_parser/include/urdf_parser/urdf_parser.h

Line 61 in ccc7d2f

URDFDOM_DLLAPI boost::shared_ptr<ModelInterface> parseURDF(const std::string &xml_string);

https://github.com/ros/urdfdom_headers/blob/56471a55d85e1be27a91a5f2f72b001d92cddb15/urdf_sensor/include/urdf_sensor/sensor.h#L157
(and others)

And weak_ptr:

https://github.com/ros/urdfdom_headers/blob/56471a55d85e1be27a91a5f2f72b001d92cddb15/urdf_model/include/urdf_model/link.h#L239

[isucan]

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?

[scpeters]

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 urdfdom2) for this type of change?

[scpeters]

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?

[wjwwood]

I'd say do it as a branch, but @isucan should make the call.

[isucan]

Please do this in a new branch, no need for a new repo.

[scpeters]

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.

ros/urdfdom_headers#13