You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally, it was impossible to "end" an unlimited option for a positional since there was no way for a positional to start taking values. The idea was that this could be a workaround:
./test a b c --test2 d --test2 e --test2 f
However, the underlying problem was fixed in CLI11 1.5, you can now use -- to end an unlimited string of values to an option. So this "greedy positional" behavior could be removed (I might even consider this for a 1.5.1 release).
Hi, have a question. I have a situation where there's one unlimited positional and one unlimited option. Like this:
If you give these arguments:
./test a b c --test2 d e f
, thena b c
ande f
will go tot1
, and onlyd
will go tot2
.I've seen in the source code:
CLI11/include/CLI/App.hpp
Line 1465 in b7c031c
Could you please explain why you design like this? I think in this situation,
d e f
should go tot2
.The text was updated successfully, but these errors were encountered: