Use getenv to get environment variables, including HOME. If you don't know for sure if they might be present, you'll have to parse the string looking for them.
You could also use the system shell and echo to let the shell do this for you.
Getenv is portable (from standard C), but using the shell to do this portably will be harder between *nix and Windows. Convention for environment variables differs between *nix and Windows too, but presumably the string is a configuration parameter that can be modified for the given platform.
If you only need to support expanding home directories rather than arbitrary environment variables, you can use the "~" convention and then "~/somedir" for your configuration strings:
std::string expand_user(std::string path) {if (not path.empty() and path[0] == '~') {assert(path.size() == 1 or path[1] == '/'); // or other error handlingchar const* home = getenv("HOME");if (home or ((home = getenv("USERPROFILE"))) {path.replace(0, 1, home);}else {char const *hdrive = getenv("HOMEDRIVE"),*hpath = getenv("HOMEPATH");assert(hdrive); // or other error handlingassert(hpath);path.replace(0, 1, std::string(hdrive) + hpath);}}return path;
}This behavior is copied from Python's os.path.expanduser, except it only handles the current user. The attempt at being platform agnostic could be improved by checking the target platform rather than blindly trying different environment variables, even though USERPROFILE, HOMEDRIVE, and HOMEPATH are unlikely to be set on Linux.
