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

Alternative version of ros::param::param with return value #97

xperroni opened this Issue Mar 30, 2015 · 3 comments


None yet
2 participants

xperroni commented Mar 30, 2015

The template function ros::param::param sets a variable either to the value of a parameter, or if not available, a predefined default value. In cases where the variable is passed straight to a constructor or function call and then disregarded, more streamlined code could be written if the result value could be retrieved as a function return value, rather than through an output variable.

For example, the code below:

std::string path;
std::string format;
double fps;

param("~path", path, "video.mpg");
param("~format", format, "MPEG");
param("~fps", fps, 30.0);

VideoRecorder recorder(path, format, fps);

Could be more succinctly written as:

VideoRecorder recorder(
    param<std::string>("~path", "video.mpg"),
    param<std::string>("~format", "MPEG"),
    param<double>("~fps", 30.0)

If an alternative definition of ros::param::param such as this was available:

template<typename T>
T param(const std::string& param_name, const T& default_val)
  T param_val;
  param(param_name, param_val, default_val);
  return value;

This comment has been minimized.


tfoote commented Mar 30, 2015

Please open this for discussion at: this repo is targeted at higher level concepts within ROS more than language specific APIs.

@tfoote tfoote closed this Mar 30, 2015


This comment has been minimized.

xperroni commented Mar 30, 2015

Done. Sorry for the blunder.


This comment has been minimized.


tfoote commented Mar 30, 2015

np. There's a lot of repos in the ros ecosystem it takes a while to learn the right places. Thanks for the quick follow up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment