
Hi, I need a way of storing/retrieving options for an application. However, although boost::program_options seemed an obvious choice, it doesn't seem able to store options - it merly reads them in. I also couldn't find any documention on how its cfg files should be formatted for use with po::parse_config_file. Could we please have a way of storing program options also? I couldn't find information on why this feature wasn't implemented in the rationale. Also, documentation on how streams should be formatted for use with po::parse_config_file is missing. Regards, Asger

Asger Mangaard wrote:
Hi,
I need a way of storing/retrieving options for an application. However, although boost::program_options seemed an obvious choice, it doesn't seem able to store options - it merly reads them in. I also couldn't find any documention on how its cfg files should be formatted for use with po::parse_config_file.
Could we please have a way of storing program options also? I couldn't find information on why this feature wasn't implemented in the rationale.
Also, documentation on how streams should be formatted for use with po::parse_config_file is missing.
It does allow options to be stored. See http://www.boost.org/doc/html/program_options/tutorial.html (in particular, section "Option Details"). Paul

Paul Giaccone wrote:
Could we please have a way of storing program options also? I couldn't find information on why this feature wasn't implemented in the rationale.
Also, documentation on how streams should be formatted for use with po::parse_config_file is missing.
It does allow options to be stored. See http://www.boost.org/doc/html/program_options/tutorial.html (in particular, section "Option Details").
I meant; to be stored back into a stream or env variable. As far as I can tell, that's not possible? Regards, Asger
participants (2)
-
Asger Mangaard
-
Paul Giaccone