Re: [Boost-users] Boost.Program_options: Parsing arguments like "+a" possible?

Subject: Re: [Boost-users] Boost.Program_options: Parsing arguments like "+a" possible?
From: boost_mailinglist_at_[hidden]
Date: 2011-08-08 06:47:35

Am 08.08.2011 12:35, schrieb Leo Cacciari:
> Hi,
> I still do not understand what are you meaning with "too many options".
> Obviously, you can not intend "too many to remember by the user",
> otherwise using a '+' would not solve your problem.
>
> If you where limited to using '-' options, as in stadard posix getopt
> function, then you could obviously run out of characters to use, more so
> if you want the character to be meaningful (as -v for 'verbose' or -o
> for 'output'). But '--' options are _long_ options, meaning that you
> could write --verbose or --output.
> How could you possibly run out of names for your options?
>

Hello,

the app is grown up step by step and a other person has taken the 
decission to use the "+" as a sign for an argument. (All the letters for 
the - are used.)
My task is more or less to rewrite the old case() parser to a new one, 
possible based on boost.program_options, to get a clear structure. At 
the moment I'm not very interesting to change the argument style, 
because all the example and more has also to be change to the new style.