jarro2783
jarro2783
Ok sure. I'll add it to the wiki.
That seems reasonable, although slightly difficult since parameters can be specified multiple times to fill up a container. It could be done with the option separator in a single option,...
I think that this would fit better with a separate options validation library, which I do have in mind to get to some day.
So just to clarify you want to call `Options::parse_positional` with an arbitrary object that represents a list of strings?
I just tried using ``` template void parse_positional(Container&&) ``` and realised that it isn't as simple as that, because passing a string matches that and then fails with a compile...
There are two ways to do this currently. You can always pass `--option` multiple times, or you could define your own type with its own parser. It's not documented, but...
Which compiler is this? I've had a few reports of these warnings. It seems like not all compilers like my attempts to do compile time calculations that are out of...
That's to fit the options into the width of a standard terminal. Can you show me some code that reproduces the problem?
That's a bit unfortunate. Is it using an old GCC standard library or does Intel have one that claims to support `regex`?
Definitely shouldn't happen on `g++-5.5.0`. If you're able to get any more out of `stdlib` about the problem that would be great.