rtt_rosnode modifies the deployer's argv about rtt_ros_integration HOT 1 CLOSED

True, this looks like a bug. But there are two possible solutions:

• copy the arguments to a std::vector<const char *> argvv and pass argvv.data() to ros::init() as suggested
• let __os_main_argc(void) return an int reference so that ros::init() can also update the counter variable (to 1 in your example)

ros::init(argc, argv, ...) is designed to modify ("consume") the remapping arguments, so that another command line parser later on would not complain about unknown options [1]. In case of rtt_rosnode this happens too late to hide the remapping arguments from the deployer, but for other plugins it might still be useful if they are loaded after rtt_rosnode. That is also the reason why you have to add a double-dash in the deployer command line before any remapping arguments [2].

As I am not aware of any other plugin that parses command line arguments and no plugin should depend on the exact order in which it is loaded anyway, I would vote for the first option.

[1] http://wiki.ros.org/roscpp/Overview/Initialization%20and%20Shutdown#Initializing_the_roscpp_Node
[2] http://wiki.ros.org/ocl#Roslaunch_for_OROCOS_components

from rtt_ros_integration.