Fytch

This feature is available on the develop branch. Commit: https://github.com/Fytch/ProgramOptions.hxx/commit/e9a7a251ecdc7f65de6e09faaf6ba11a401b3421 Exemplary usage: ```cpp auto&& foo = parser[ "foo" ] .mandatory(); ``` **However**: There's a problem in that implementation right now:...

To illustrate the aforementioned issue, consider this example: ```cpp #include #include int main( int argc, char** argv ) { po::parser parser; auto&& help = parser[ "help" ] .abbreviation( '?' )...

Hello Thanks a lot for your feedback. I appreciate every suggestion and criticism. (1.1) > `O.get()` Well, `O.get().u32` is actually both shorter to type and more expressive (it tells you...

Hello (1) I agree, `get` templates are pretty commonplace. I'll have a look into that, if you're still interested. Would you mind testing it once I've implemented it? I envisioned...

Hello > Could you not have a .verbose() member Yes, a flag makes much more sense. In retrospect, I have no idea why I implemented it as a macro, honestly....

There's a member function [`parser::silent()`](https://github.com/Fytch/ProgramOptions.hxx/tree/develop#miscellaneous-functions) implemented on the develop branch, which does what you suggested. There's also a `parser::verbose(std::ostream&)` that lets you redirect the output, e.g. into a log file....

Hi > it is always convenient to be able to print out the state of an object Indeed, that would be a helpful feature. I was thinking about printing the...

I agree, the output format should be clearer. I'll try out some things next week. > You'd have to 'pretty print' JSON, at which point I'm not sure it is...

I think it would be best to offer const iterators in `parser` so that the programmer can freely view all options (in the order added) and build his own output...

I would also be very interested in this feature. I think the files in `AppData\Local\qBittorrent\BT_backup` contain hard paths which are not usable by both Windows and Linux but if the...