clipp
clipp copied to clipboard
muellan
easy to use, powerful & expressive command line argument parsing for modern C++ / single header / usage & doc generation
fix for MSVC2019 going bonkers about the various `struct active` in the tests mixing them up in monolithic builds: by placing each within its own namespace do we prevent this...
- added `man_page::program_basename(path)` API - made this part of the `man_page::program_name(path)` APIs - ensure the SYNOPSIS output on Windows boxes lists the program **name** instead of its entire **path** (cherrypicked...
fix errors in MSVC build due to unsupported compiler -W warnings configuration (cherrypicked off https://github.com/GerHobbelt/clipp master branch; original commit tested with latest MSVC2019)
Hi, some time ago I stumbled upon a problem with CLI, which consisted of three or more commands. I have found a work-around and I am posting it here hoping...
Code: ``` auto cli = (option("--a") & value("A") % "help a", option("-b") & value("B") % "help b") % "group 1"; std::cout
I would like to be able to parse a struct containing `std::optional` fields. For example: ```cpp struct arg_values { std::optional pid; } values; auto cli = ( clipp::option("--pid") & clipp::opt_integer("PID",...
Is it possible for the parameter matching to be case insensitive ? For example, option("-ext") would parse correctly with "-Ext", "-ext", "-EXT", "-eXt", "-ExT"
I could have misunderstood how to use clipp properly but I have found using multiple optional numeric values with leading dot leads to incorrect parsing, for example: double a, b;...
Used to test for #53 and #54 Only adding a switch to allow for testing, not touching travis and appveyor configs as I do not know which specific configurations are...
## Problem ## When using the library on Windows, with the header Windows.h included, I get an error in the places that ``` std::min ``` is used. Wherever ``` min...
