Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
roscpp param::init() needs to parse mappings using yaml-cpp to be consistent with rospy #1498
ROS users have many times observed weird behavior inconsistencies between rospy/rosparam and roscpp when using parameters (#1339, #1153, #445, #390, #436). I'm not sure about the other client libraries.
I think there needs to be an agreement made that this is unacceptable: users of nodes really should not care whether the nodes are written using rospy, roscpp, rosrust or whatever client library... to just know what kind of behavior they can expect from
I hope everybody would agree that rospy should be taken as the reference implementation (as e.g.
I see two action points now:
Knowing about #1496, I can work on the implementation. Just before I start doing so, I'd like to know it is something that has a high probability of being merged (not necessarily to melodic or older releases, but at least to current master). And another question - is it okay to introduce yaml-cpp as a dependency to
This change will definitely change behavior of some roscpp programs, but as I said in #436 , it should only break code that is already broken (but the authors did not notice/care).
Maybe it would be good to start with a REP to formalize this. That document could then also clearly describe what breaking changes are necessary to make the different client libraries consistent. Depending how these breaking changes look like the decision if / when it can be merged will be made.