Re: [Boost-users] [program_options] Parsing config files

Subject: Re: [Boost-users] [program_options] Parsing config files
From: Michael Powell (mwpowellhtx_at_[hidden])
Date: 2013-08-08 12:37:53

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 <mwpowellhtx_at_[hidden]> wrote:
> Great. Thank ye sir!
>
> On Thu, Aug 8, 2013 at 11:30 AM, Rhys Ulerich <rhys.ulerich_at_[hidden]> 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_at_[hidden]
>> http://lists.boost.org/mailman/listinfo.cgi/boost-users