How does boost::program_options
parse or manage an input when both multitoken and positional options are allowed?
For example:
./app.sample pos1 --multitokenoption a b c d pos2
How does boost know when a multitokenoption
finishes and a positional option begins?
Obviously, the most logical allowed behaviour would be that a multitoken option must be present as last parameter, just as happens with default arguments in function parameters, but the documentation says nothing about it.