Indiana Kernick

@tdegeus > Thanks for the library! Don't thank me! 😄 I'm just a guy who happened to see this issue. I'm not a contributor. As for modernising the interface, `DocoptArgumentError`...

> change for change's sake can do more harm All three of us agree on that. I think there's a lot of minor (but breaking) improvements that could be made...

This actually doesn't quite work properly. `-f` and `-b` are added to the map instead of `--foo` and `--bar`. I really think this feature is useful for creating _beautiful_ command-line...

What you’re trying to do is not impossible. You just haven’t got the syntax quite right. Try this: ``` Usage: my_program [--output=] Options: -o, --output specify output file [default: ./default.h]...

That’s because `file path` is two separate arguments. You need to use a backslash. `file\ path`.

For something like this, you might want to request it [upstream](https://github.com/docopt/docopt)

I started working on this and I got something that seems to work. [See for yourself](https://github.com/Kerndog73/docopt.cpp/tree/single_header). Though the problem is that docopt is not written as a header-only library. Simply...

It seems like almost all errors fall through to [this point](https://github.com/docopt/docopt.cpp/blob/69682578d4dbb59b297a15ea537f2b1b8735c7bc/docopt.cpp#L655). Simply printing out all the arguments that the user passed isn't useful. That line might as well be `throw...

@jaredgrubb Perhaps you could review [some PRs](https://github.com/docopt/docopt.cpp/pull/126) 😉. Breaking changes might be acceptable after a release...

You could move conversion from string to long into a separate function. ```C++ bool isLong() const { return kind == Kind::Long; } long asLong() const { throwIfNotKind(Kind::Long); return variant.longValue; }...