André Müller

You did everything right. It is a bug. I've just discovered where it goes wrong. You can use this workaround, until I have a fix ready: ```cpp auto dummy =...

You could achieve that by separating the definitions of the commands and options from the parsing control flow logic: ```cpp auto opts = ( option("-a"), option("-b"), option("-c") ); auto cmds...

Yeah that seems to be a bug. I also think that I already know where it goes wrong.

Good idea. I should definitly add built-in support for `std::optional`.

I have though about this, too. It is however not as straightforward as it might seem. The interface looks like you could "bind" variables to value parameters. That is however...

BTW, you could always implement your own factory function: ```cpp template clipp::parameter documented_value(const std::string& name, Target& tgt, const std::string& docstr) { using std::to_string; return clipp::value(name,tgt).doc(docstr + "(default: " + to_string(tgt)...

Error messages have to be generated by the developer. You can check, if parsing fails, either per parameter (see [here](https://github.com/muellan/clipp#basic-error-handling)) or by analyzing the parsing result (see [here](https://github.com/muellan/clipp#parsing)). At the...

That shouldn't happen, so I consider this to be a bug. It seems to break if the args after the stand-alone `--` have `--` as their prefix. A quick&dirty fix...

Yeah this is a bug. I guess I just never though of having only one joinable option on its own. I'll fix it, but I don't know how soon I...

I see the problem. Unfortunately, the expressions `( object )` and `object` are equivalent and C++ doesn't offer any way to distinguish between them. But the following works for me:...