Yes, that was (sad) conclusion that I was coming to. Thanks for the confirmation, though.
Many configurations use lists or tab & linefeed separated tables of data, where they don't want to specify an option in front of each and every element. It would be nice if the config file parser used the same semantics as the command line in order to enable this functionality. I suspect it wouldn't be all that hard either, what do you think?
Zak
It's not possible, as I never saw a config file with positional options.Zachary wrote:
> I've been using program_options quite happily and successfully for a short
> while now and would like to take this opportunity to express my gratitude.
>
> Is there a way to extract postional args from config file, though? The
> headers seem to indicate that it's possible include_positional flag, but I
> haven't been able to find something workable in the documentation or
> mailing lists.
The 'include_positional' you mention is defined like this:
/** Controls if the 'collect_unregistered' function should
include positional options, or not. */
enum collect_unrecognized_mode
{ include_positional, exclude_positional };
so it only applies to collect_unregistered function. As config file
parser will never return positional options, 'include_positional' is
of no use.
Does this clarifies things?
- Volodya
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users