On Fri, 2012-12-28 at 00:43 +1100, Joshua Boyce wrote:
On Thu, Dec 27, 2012 at 4:56 AM, ST <smntov@gmail.com> wrote:
Hi,
It would be great to implement support for open-end options, something like that:
item_1 = 23 item_2 = 45 ... item_N = 465
The idea is to to be able to provide following input:
configOptions.add_options() ("item_", value<int>(), "items");
now if add_options() sees a key that ends with a "_" it accepts all options with keys that start with item_, no matter what comes after it, and treat all of them as int . Nesting should also be possible - like this: "item_.subitem_.subsubitem_" (item_3.subitem_FOO.subsubitem_34 should be a valid option key). I can try to implement it, however only if it will have a chance to be merged into the boost library. Whom should I contact regarding this?
Thank you, Simone
I have a definite use case for the type of open-ended options you're proposing here.
It seems you want to get into contact with Vladimir Prus. He's an active member of the mailing list, so you should have no issues getting a response.
He doesn't seem to be that active nowdays. I tried to get in touch with him during last month but without success. I wrote a workaround that works fine for me. So I decided to open 2 new tickets and close the case. Should there be any progress I'll be glad to hear about it. https://svn.boost.org/trac/boost/ticket/7932 https://svn.boost.org/trac/boost/ticket/7933 Regards, Simone