How about for non-value type options: i.e. the key just exists.

For instance, "--some-time-out 1000" works well. However, what about for "--simple-flag" ?

So far I seem to be getting parse errors...

This bit me too. IIRC, 'simple-flag=' with no value. - Rhys

Works like a champ! Last question I think: when it comes to prioritizing options preference, I'd like to prefer command line over configuration file: in other words, give the end-user an opportunity to override the configuration file on the command line. So, to do this, first parse the configuration file? Then parse the command line? Or vice versa? Thank you... On Thu, Aug 8, 2013 at 11:35 AM, Michael Powell wrote:

Great. Thank ye sir!

On Thu, Aug 8, 2013 at 11:30 AM, Rhys Ulerich wrote:

...

...

How about for non-value type options: i.e. the key just exists.

For instance, "--some-time-out 1000" works well. However, what about for "--simple-flag" ?

So far I seem to be getting parse errors...

This bit me too. IIRC, 'simple-flag=' with no value.

- Rhys _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Can you confirm? On Thu, Aug 8, 2013 at 12:39 PM, Rhys Ulerich wrote:

...

Last question I think: when it comes to prioritizing options preference, I'd like to prefer command line over configuration file: in other words, give the end-user an opportunity to override the configuration file on the command line.

I do CLI first and then any option files.

I can do configuration files, but it doesn't seem to matter when I do one versus the other. Once it is specified in the configuration file, that one takes precedence. Perhaps there is some parse option I can use to override options? I'd like to do configuration file first, then override with CLI, if possible. Of course where po::value() is involved, that could get interesting. Thank you...

- Rhys _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

I stand corrected. It works! Was a stuck-ness in a static library of ours. I cleaned and rebuilt that and now it works. Sorry for any confusion... On Thu, Aug 8, 2013 at 2:02 PM, Michael Powell wrote:

...

On Thu, Aug 8, 2013 at 11:37 AM, Michael Powell wrote:

...

Works like a champ!

Last question I think: when it comes to prioritizing options preference, I'd like to prefer command line over configuration file: in other words, give the end-user an opportunity to override the configuration file on the command line.

So, to do this, first parse the configuration file? Then parse the command line? Or vice versa?

Doesn't seem to matter which order I put them in. The configuration file always wins. I'd rather it was the command line that wins.

Interesting, and somewhat expected, that when I specify a mutually exclusive set of options, the process runs and parses and responds to the options as expected.

Anyone?

Thank ye...

...

Thank you...

On Thu, Aug 8, 2013 at 11:35 AM, Michael Powell wrote:

...

Great. Thank ye sir!

On Thu, Aug 8, 2013 at 11:30 AM, Rhys Ulerich wrote:

...

...

How about for non-value type options: i.e. the key just exists.

For instance, "--some-time-out 1000" works well. However, what about for "--simple-flag" ?

So far I seem to be getting parse errors...

This bit me too. IIRC, 'simple-flag=' with no value.

- Rhys _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users