Boost C++ Libraries: Ticket #2727: program_options ill behaviour with unrecognized options

cc set

Wed, 15 Jul 2009 02:10:55 GMT

cc dcnieho@… added

Yeah, there must be a cool reason why the original_token field is outputted as the unrecognized options, but i think instead we could simply output the string_key, which is set for all (registered and unregistered) options. if mode == include_positional && options[i].position_key != -1, add the value for that entry to the output vector. That should do the trick.

proposed diff:

Index: parsers.hpp
===================================================================
--- parsers.hpp (revision 54915)
+++ parsers.hpp (working copy)
@@ -129,13 +129,12 @@
         std::vector< std::basic_string<charT> >  result;
         for(unsigned i = 0; i < options.size(); ++i)
         {
-            if (options[i].unregistered ||
-                (mode == include_positional && options[i].position_key != -1))
-            {
-                copy(options[i].original_tokens.begin(),
-                     options[i].original_tokens.end(),
+            if (options[i].unregistered)
+                result.push_back(options[i].string_key);
+            else if (mode == include_positional && options[i].position_key != -
1)
+                copy(options[i].value.begin(),
+                     options[i].value.end(),
                      back_inserter(result));
-            }
         }
         return result;
     }

owner, status, milestone changed

Sascha Ochsenknecht — Tue, 08 Dec 2009 07:40:59 GMT

owner changed from Vladimir Prus to Sascha Ochsenknecht
status new → assigned
milestone Boost 1.38.0 → Boost 1.42.0

The 'cool' reason is that original_tokens are original :-), i.e. they are stored untouched like they appeared on cmdline/config file. The purpose of collect_unrecognized() is to return them and the user can pass them to an own parser implementation.

status changed; resolution set

Sascha Ochsenknecht — Tue, 08 Dec 2009 07:45:46 GMT

status assigned → closed
resolution → fixed

(In [58233]) config file parser now stores original_tokens, Fixes #2727

Sascha Ochsenknecht — Tue, 08 Dec 2009 07:48:17 GMT

I just checked it a patch which uses a different approach than the above proposal. I decided to store the original_tokens when parsing the config file and keep the collect function untouched.