id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
6991	Provide a way to disable interspersed arguments	driscoll@…	Vladimir Prus	"I'm trying to write a program that wraps other programs, and allowing switches to come after the first positional argument in this situation is very annoying from the user's standpoint.

If I define the flag --flag in my wrapper, it means that
{{{    
    my-program target-program --flag
}}}
won't run {{{target-program --flag}}} as one would hope, but will treat {{{--flag}}} as an argument to my program.

This means that the user has to run {{{my-program -- target-program --flag}}} every time, which is both annoying and goes against how most such programs work on Unix. (You never see someone say ""run {{{sudo -- apt-get install blah}}}."" Or xargs, env, nohup, etc.)

As far as I'm concerned, this problem is a showstopper for using the stock Boost po for this sort of program. If the Gflags library didn't have the same limitation, I'd be using it right now instead of having patched Boost. :-)

So I request a setting to disable this sort of interspersed arguments.

----

Fortunately, (one possible) fix seems to be pretty simple from what I can tell. I'll follow up this post with a patch after I get things cleaned back up and such."	Feature Requests	new	To Be Determined	program_options	Boost 1.49.0	Problem			mateusz@…