No take_last specifier for add_flag

[bergercookie]

In the CLI11 tutorials it says that:

This will bind the flag -f to the boolean my_flag. After the parsing step, my_flag will be false if the flag was not found on the command line, or true if it was. By default, it will be allowed any number of times, but if you explicitly1 request ->take_last(false), it will only be allowed once; passing something like ./my_app -f -f or ./my_app -ff will throw a ParseError with a nice help description.

However, after including the CLI11.hpp file and using this kind of expression I get the error:

no member named 'take_last' in 'CLI::Option'

The expression I used is the following:

bool runSingleThread;
subcommand->add_flag("-s,--singleThread", runSingleThread, "Split execution into multiple threads")
      ->take_last(false);

Is there something I did wrong? Is this option implemented in a later version than the one I'm using?

Cheers

[henryiii]

It was added in 1.3. Is that the one you are using? Otherwise, that looks right.

[bergercookie]

Ah, that explains.. I'm still using the v1.2.0 version. Thanks for sorting this. Keep up the good work.

On Tue, Dec 12, 2017 at 2:23 PM Henry Schreiner ***@***.***> wrote: It was added in 1.3. Is that the one you are using? Otherwise, that looks right. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#62 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFjBj6rVMCDNnd5La4srq02m70w910waks5s_oxbgaJpZM4Q-ya8> .

-- Nikos Koukis School of Mechanical Engineering National Technical University of Athens nickkouk@gmail.com +30 6985827375

[henryiii]

I'd recommend moving up to 1.3, should be painless for the most part (check the release notes), and the error messages are much better. But, fun fact, 1.2 actually defaults to and only allows the take_last(false) behavior, so you should be okay either way.