GithubHelp home page GithubHelp logo

taywee / args Goto Github PK

View Code? Open in Web Editor NEW
1.4K 41.0 156.0 2.78 MB

A simple header-only C++ argument parser library. Supposed to be flexible and powerful, and attempts to be compatible with the functionality of the Python standard argparse library (though not necessarily the API).

License: MIT License

Python 0.69% Makefile 0.13% C++ 98.36% CMake 0.61% Starlark 0.08% Meson 0.13%

args's Introduction

args

This library is considered feature-complete by its creator. It will still receive bug fixes, and good pull requests will be accepted, but no new major functionality or API changes will be added to this codebase.

Cpp Standard Travis status AppVeyor status Coverage Status Read the Docs

A simple, small, flexible, single-header C++11 argument parsing library.

This is designed to appear somewhat similar to Python's argparse, but in C++, with static type checking, and hopefully a lot faster (also allowing fully nestable group logic, where Python's argparse does not).

UTF-8 support is limited at best. No normalization is performed, so non-ascii characters are very best kept out of flags, and combined glyphs are probably going to mess up help output if you use them. Most UTF-8 necessary for internationalization should work for most cases, though heavily combinatory UTF alphabets may wreak havoc.

This program is MIT-licensed, so you can use the header as-is with no restrictions. I'd appreciate attribution in a README, Man page, or something if you are feeling generous, but all that's required is that you don't remove the license and my name from the header of the args.hxx file in source redistributions (ie. don't pretend that you wrote it). I do welcome additions and updates wherever you feel like contributing code.

The API documentation can be found at https://taywee.github.io/args

The code can be downloaded at https://github.com/Taywee/args

There are also somewhat extensive examples below.

You can find the complete test cases at https://github.com/Taywee/args/blob/master/test.cxx, which should very well describe the usage, as it's built to push the boundaries.

What does it do?

It:

  • Lets you handle flags, flag+value, and positional arguments simply and elegantly, with the full help of static typechecking.
  • Allows you to use your own types in a pretty simple way.
  • Lets you use count flags, and lists of all argument-accepting types.
  • Allows full validation of groups of required arguments, though output isn't pretty when something fails group validation. User validation functions are accepted. Groups are fully nestable.
  • Generates pretty help for you, with some good tweakable parameters.
  • Lets you customize all prefixes and most separators, allowing you to create an infinite number of different argument syntaxes.
  • Lets you parse, by default, any type that has a stream extractor operator for it. If this doesn't work for your uses, you can supply a function and parse the string yourself if you like.
  • Lets you decide not to allow separate-argument value flags or joined ones (like disallowing --foo bar, requiring --foo=bar, or the inverse, or the same for short options).
  • Allows you to create subparsers, to reuse arguments for multiple commands and to refactor your command's logic to a function or lambda.
  • Allows one value flag to take a specific number of values (like --foo first second, where --foo slurps both arguments).
  • Allows you to have value flags only optionally accept values.
  • Provides autocompletion for bash.

What does it not do?

There are tons of things this library does not do!

It will not ever:

  • Allow you to intermix multiple different prefix types (eg. ++foo and --foo in the same parser), though shortopt and longopt prefixes can be different.
  • Allow you to make flags sensitive to order (like gnu find), or make them sensitive to relative ordering with positionals. The only orderings that are order-sensitive are:
    • Positionals relative to one-another
    • List positionals or flag values to each of their own respective items
  • Allow you to use a positional list before any other positionals (the last argument list will slurp all subsequent positional arguments). The logic for allowing this would be a lot more code than I'd like, and would make static checking much more difficult, requiring us to sort std::string arguments and pair them to positional arguments before assigning them, rather than what we currently do, which is assigning them as we go for better simplicity and speed. The library doesn't stop you from trying, but the first positional list will slurp in all following positionals

How do I install it?

sudo make install

Or, to install it somewhere special (default is /usr/local):

sudo make install DESTDIR=/opt/mydir

You can also copy the file into your source tree, if you want to be absolutely sure you keep a stable API between projects.

If you prefer other installation methods, many standard ones are available and included, including CMake, conan, buck, and meson. An example CMake file using args is included in the examples directory.

I also want man pages.

make doc/man
sudo make installman

This requires Doxygen

I want the doxygen documentation locally

doxygen Doxyfile

Your docs are now in doc/html

How to depend on it using tipi.build?

Simply add the following entry to your .tipi/deps file

{
    "taywee/args": { "@": "6.4.1" }
}

You can optionally remove the @ section to target HEAD easily.

How do I use it?

Create an ArgumentParser, modify its attributes to fit your needs, add arguments through regular argument objects (or create your own), and match them with an args::Matcher object (check its construction details in the doxygen documentation.

Then you can either call it with args::ArgumentParser::ParseCLI for the full command line with program name, or args::ArgumentParser::ParseArgs with just the arguments to be parsed. The argument and group variables can then be interpreted as a boolean to see if they've been matched.

All variables can be pulled (including the boolean match status for regular args::Flag variables) with args::get.

Group validation is weird. How do I get more helpful output for failed validation?

This is unfortunately not possible, given the power of the groups available. For instance, if you have a group validation that works like (A && B) || (C && (D XOR E)), how is this library going to be able to determine what exactly when wrong when it fails? It only knows that the entire expression evaluated false, not specifically what the user did wrong (and this is doubled over by the fact that validation operations are ordinary functions without any special meaning to the library). As you are the only one who understands the logic of your program, if you want useful group messages, you have to catch the ValidationError as a special case and check your own groups and spit out messages accordingly.

Is it developed with regression tests?

Yes. tests.cxx in the git repository has a set of standard tests (which are still relatively small in number, but I would welcome some expansion here), and thanks to Travis CI and AppVeyor, these tests run with every single push:

% make runtests
g++ test.cxx -o test.o -I. -std=c++11 -O2 -c -MMD
g++ -o test test.o -std=c++11 -O2
./test
===============================================================================
All tests passed (74 assertions in 15 test cases)

%

The testing library used is Catch.

Examples

All the code examples here will be complete code examples, with some output.

Simple example:

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::HelpFlag help(parser, "help", "Display this help menu", {'h', "help"});
    args::CompletionFlag completion(parser, {"complete"});
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (const args::Completion& e)
    {
        std::cout << e.what();
        return 0;
    }
    catch (const args::Help&)
    {
        std::cout << parser;
        return 0;
    }
    catch (const args::ParseError& e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    return 0;
}
 % ./test
 % ./test -h
  ./test {OPTIONS} 

    This is a test program. 

  OPTIONS:

      -h, --help         Display this help menu 

    This goes after the options. 
 % 

Boolean flags, special group types, different matcher construction:

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::Group group(parser, "This group is all exclusive:", args::Group::Validators::Xor);
    args::Flag foo(group, "foo", "The foo flag", {'f', "foo"});
    args::Flag bar(group, "bar", "The bar flag", {'b'});
    args::Flag baz(group, "baz", "The baz flag", {"baz"});
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    catch (args::ValidationError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    if (foo) { std::cout << "foo" << std::endl; }
    if (bar) { std::cout << "bar" << std::endl; }
    if (baz) { std::cout << "baz" << std::endl; }
    return 0;
}
 % ./test   
Group validation failed somewhere!
  ./test {OPTIONS} 

    This is a test program. 

  OPTIONS:

                         This group is all exclusive:
        -f, --foo          The foo flag 
        -b                 The bar flag 
        --baz              The baz flag 

    This goes after the options. 
 % ./test -f
foo
 % ./test --foo
foo
 % ./test --foo -f
foo
 % ./test -b      
bar
 % ./test --baz
baz
 % ./test --baz -f
Group validation failed somewhere!
  ./test {OPTIONS} 

    This is a test program. 
...
 % ./test --baz -fb
Group validation failed somewhere!
  ./test {OPTIONS} 
...
 % 

Argument flags, Positional arguments, lists

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::HelpFlag help(parser, "help", "Display this help menu", {'h', "help"});
    args::ValueFlag<int> integer(parser, "integer", "The integer flag", {'i'});
    args::ValueFlagList<char> characters(parser, "characters", "The character flag", {'c'});
    args::Positional<std::string> foo(parser, "foo", "The foo position");
    args::PositionalList<double> numbers(parser, "numbers", "The numbers position list");
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    catch (args::ValidationError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    if (integer) { std::cout << "i: " << args::get(integer) << std::endl; }
    if (characters) { for (const auto ch: args::get(characters)) { std::cout << "c: " << ch << std::endl; } }
    if (foo) { std::cout << "f: " << args::get(foo) << std::endl; }
    if (numbers) { for (const auto nm: args::get(numbers)) { std::cout << "n: " << nm << std::endl; } }
    return 0;
}
% ./test -h
  ./test {OPTIONS} [foo] [numbers...] 

    This is a test program. 

  OPTIONS:

      -h, --help         Display this help menu 
      -i integer         The integer flag 
      -c characters      The character flag 
      foo                The foo position 
      numbers            The numbers position list 
      "--" can be used to terminate flag options and force all following
      arguments to be treated as positional options 

    This goes after the options. 
 % ./test -i 5
i: 5
 % ./test -i 5.2
Argument 'integer' received invalid value type '5.2'
  ./test {OPTIONS} [foo] [numbers...] 
 % ./test -c 1 -c 2 -c 3
c: 1
c: 2
c: 3
 % 
 % ./test 1 2 3 4 5 6 7 8 9
f: 1
n: 2
n: 3
n: 4
n: 5
n: 6
n: 7
n: 8
n: 9
 % ./test 1 2 3 4 5 6 7 8 9 a
Argument 'numbers' received invalid value type 'a'
  ./test {OPTIONS} [foo] [numbers...] 

    This is a test program. 
...

Commands

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser p("git-like parser");
    args::Group commands(p, "commands");
    args::Command add(commands, "add", "add file contents to the index");
    args::Command commit(commands, "commit", "record changes to the repository");
    args::Group arguments(p, "arguments", args::Group::Validators::DontCare, args::Options::Global);
    args::ValueFlag<std::string> gitdir(arguments, "path", "", {"git-dir"});
    args::HelpFlag h(arguments, "help", "help", {'h', "help"});
    args::PositionalList<std::string> pathsList(arguments, "paths", "files to commit");

    try
    {
        p.ParseCLI(argc, argv);
        if (add)
        {
            std::cout << "Add";
        }
        else
        {
            std::cout << "Commit";
        }

        for (auto &&path : pathsList)
        {
            std::cout << ' ' << path;
        }

        std::cout << std::endl;
    }
    catch (args::Help)
    {
        std::cout << p;
    }
    catch (args::Error& e)
    {
        std::cerr << e.what() << std::endl << p;
        return 1;
    }
    return 0;
}
% ./test -h
  ./test COMMAND [paths...] {OPTIONS}

    git-like parser

  OPTIONS:

      commands
        add                               add file contents to the index
        commit                            record changes to the repository
      arguments
        --git-dir=[path]
        -h, --help                        help
        paths...                          files
      "--" can be used to terminate flag options and force all following
      arguments to be treated as positional options

% ./test add 1 2
Add 1 2

Refactoring commands

#include <iostream>
#include "args.hxx"

args::Group arguments("arguments");
args::ValueFlag<std::string> gitdir(arguments, "path", "", {"git-dir"});
args::HelpFlag h(arguments, "help", "help", {'h', "help"});
args::PositionalList<std::string> pathsList(arguments, "paths", "files to commit");

void CommitCommand(args::Subparser &parser)
{
    args::ValueFlag<std::string> message(parser, "MESSAGE", "commit message", {'m'});
    parser.Parse();

    std::cout << "Commit";

    for (auto &&path : pathsList)
    {
        std::cout << ' ' << path;
    }

    std::cout << std::endl;

    if (message)
    {
        std::cout << "message: " << args::get(message) << std::endl;
    }
}

int main(int argc, const char **argv)
{
    args::ArgumentParser p("git-like parser");
    args::Group commands(p, "commands");
    args::Command add(commands, "add", "add file contents to the index", [&](args::Subparser &parser)
    {
        parser.Parse();
        std::cout << "Add";

        for (auto &&path : pathsList)
        {
            std::cout << ' ' << path;
        }

        std::cout << std::endl;
    });

    args::Command commit(commands, "commit", "record changes to the repository", &CommitCommand);
    args::GlobalOptions globals(p, arguments);

    try
    {
        p.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << p;
    }
    catch (args::Error& e)
    {
        std::cerr << e.what() << std::endl << p;
        return 1;
    }
    return 0;
}
% ./test -h
  ./test COMMAND [paths...] {OPTIONS}

    git-like parser

  OPTIONS:

      commands
        add                               add file contents to the index
        commit                            record changes to the repository
      arguments
        --git-dir=[path]
        -h, --help                        help
        paths...                          files
      "--" can be used to terminate flag options and force all following
      arguments to be treated as positional options

% ./test add 1 2
Add 1 2

% ./test commit -m "my commit message" 1 2
Commit 1 2
message: my commit message

Custom type parsers (here we use std::tuple)

#include <iostream>
#include <tuple>

std::istream& operator>>(std::istream& is, std::tuple<int, int>& ints)
{
    is >> std::get<0>(ints);
    is.get();
    is >> std::get<1>(ints);
    return is;
}

#include <args.hxx>

struct DoublesReader
{
    void operator()(const std::string &name, const std::string &value, std::tuple<double, double> &destination)
    {
        size_t commapos = 0;
        std::get<0>(destination) = std::stod(value, &commapos);
        std::get<1>(destination) = std::stod(std::string(value, commapos + 1));
    }
};

int main(int argc, char **argv)
{
    args::ArgumentParser parser("This is a test program.");
    args::Positional<std::tuple<int, int>> ints(parser, "INTS", "This takes a pair of integers.");
    args::Positional<std::tuple<double, double>, DoublesReader> doubles(parser, "DOUBLES", "This takes a pair of doubles.");
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    if (ints)
    {
        std::cout << "ints found: " << std::get<0>(args::get(ints)) << " and " << std::get<1>(args::get(ints)) << std::endl;
    }
    if (doubles)
    {
        std::cout << "doubles found: " << std::get<0>(args::get(doubles)) << " and " << std::get<1>(args::get(doubles)) << std::endl;
    }
    return 0;
}
 % ./test -h
Argument could not be matched: 'h'
  ./test [INTS] [DOUBLES] 

    This is a test program. 

  OPTIONS:

      INTS               This takes a pair of integers. 
      DOUBLES            This takes a pair of doubles. 

 % ./test 5
ints found: 5 and 0
 % ./test 5,8
ints found: 5 and 8
 % ./test 5,8 2.4,8
ints found: 5 and 8
doubles found: 2.4 and 8
 % ./test 5,8 2.4, 
terminate called after throwing an instance of 'std::invalid_argument'
  what():  stod
zsh: abort      ./test 5,8 2.4,
 % ./test 5,8 2.4 
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::basic_string: __pos (which is 4) > this->size() (which is 3)
zsh: abort      ./test 5,8 2.4
 % ./test 5,8 2.4-7
ints found: 5 and 8
doubles found: 2.4 and 7
 % ./test 5,8 2.4,-7
ints found: 5 and 8
doubles found: 2.4 and -7

As you can see, with your own types, validation can get a little weird. Make sure to check and throw a parsing error (or whatever error you want to catch) if you can't fully deduce your type. The built-in validator will only throw if there are unextracted characters left in the stream.

Long descriptions and proper wrapping and listing

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser parser("This is a test program with a really long description that is probably going to have to be wrapped across multiple different lines.  This is a test to see how the line wrapping works", "This goes after the options.  This epilog is also long enough that it will have to be properly wrapped to display correctly on the screen");
    args::HelpFlag help(parser, "HELP", "Show this help menu.", {'h', "help"});
    args::ValueFlag<std::string> foo(parser, "FOO", "The foo flag.", {'a', 'b', 'c', "a", "b", "c", "the-foo-flag"});
    args::ValueFlag<std::string> bar(parser, "BAR", "The bar flag.  This one has a lot of options, and will need wrapping in the description, along with its long flag list.", {'d', 'e', 'f', "d", "e", "f"});
    args::ValueFlag<std::string> baz(parser, "FOO", "The baz flag.  This one has a lot of options, and will need wrapping in the description, even with its short flag list.", {"baz"});
    args::Positional<std::string> pos1(parser, "POS1", "The pos1 argument.");
    args::PositionalList<std::string> poslist1(parser, "POSLIST1", "The poslist1 argument.");
    args::Positional<std::string> pos2(parser, "POS2", "The pos2 argument.");
    args::PositionalList<std::string> poslist2(parser, "POSLIST2", "The poslist2 argument.");
    args::Positional<std::string> pos3(parser, "POS3", "The pos3 argument.");
    args::PositionalList<std::string> poslist3(parser, "POSLIST3", "The poslist3 argument.");
    args::Positional<std::string> pos4(parser, "POS4", "The pos4 argument.");
    args::PositionalList<std::string> poslist4(parser, "POSLIST4", "The poslist4 argument.");
    args::Positional<std::string> pos5(parser, "POS5", "The pos5 argument.");
    args::PositionalList<std::string> poslist5(parser, "POSLIST5", "The poslist5 argument.");
    args::Positional<std::string> pos6(parser, "POS6", "The pos6 argument.");
    args::PositionalList<std::string> poslist6(parser, "POSLIST6", "The poslist6 argument.");
    args::Positional<std::string> pos7(parser, "POS7", "The pos7 argument.");
    args::PositionalList<std::string> poslist7(parser, "POSLIST7", "The poslist7 argument.");
    args::Positional<std::string> pos8(parser, "POS8", "The pos8 argument.");
    args::PositionalList<std::string> poslist8(parser, "POSLIST8", "The poslist8 argument.");
    args::Positional<std::string> pos9(parser, "POS9", "The pos9 argument.");
    args::PositionalList<std::string> poslist9(parser, "POSLIST9", "The poslist9 argument.");
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    catch (args::ValidationError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    return 0;
}
 % ./test -h
  ./test {OPTIONS} [POS1] [POSLIST1...] [POS2] [POSLIST2...] [POS3]
      [POSLIST3...] [POS4] [POSLIST4...] [POS5] [POSLIST5...] [POS6]
      [POSLIST6...] [POS7] [POSLIST7...] [POS8] [POSLIST8...] [POS9]
      [POSLIST9...] 

    This is a test program with a really long description that is probably going
    to have to be wrapped across multiple different lines. This is a test to see
    how the line wrapping works 

  OPTIONS:

      -h, --help         Show this help menu. 
      -a FOO, -b FOO, -c FOO, --a FOO, --b FOO, --c FOO, --the-foo-flag FOO
                         The foo flag. 
      -d BAR, -e BAR, -f BAR, --d BAR, --e BAR, --f BAR
                         The bar flag. This one has a lot of options, and will
                         need wrapping in the description, along with its long
                         flag list. 
      --baz FOO          The baz flag. This one has a lot of options, and will
                         need wrapping in the description, even with its short
                         flag list. 
      POS1               The pos1 argument. 
      POSLIST1           The poslist1 argument. 
      POS2               The pos2 argument. 
      POSLIST2           The poslist2 argument. 
      POS3               The pos3 argument. 
      POSLIST3           The poslist3 argument. 
      POS4               The pos4 argument. 
      POSLIST4           The poslist4 argument. 
      POS5               The pos5 argument. 
      POSLIST5           The poslist5 argument. 
      POS6               The pos6 argument. 
      POSLIST6           The poslist6 argument. 
      POS7               The pos7 argument. 
      POSLIST7           The poslist7 argument. 
      POS8               The pos8 argument. 
      POSLIST8           The poslist8 argument. 
      POS9               The pos9 argument. 
      POSLIST9           The poslist9 argument. 
      "--" can be used to terminate flag options and force all following
      arguments to be treated as positional options 

    This goes after the options. This epilog is also long enough that it will
    have to be properly wrapped to display correctly on the screen 
 %

Customizing parser prefixes

dd-style

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser parser("This command likes to break your disks");
    parser.LongPrefix("");
    parser.LongSeparator("=");
    args::HelpFlag help(parser, "HELP", "Show this help menu.", {"help"});
    args::ValueFlag<long> bs(parser, "BYTES", "Block size", {"bs"}, 512);
    args::ValueFlag<long> skip(parser, "BYTES", "Bytes to skip", {"skip"}, 0);
    args::ValueFlag<std::string> input(parser, "BLOCK SIZE", "Block size", {"if"});
    args::ValueFlag<std::string> output(parser, "BLOCK SIZE", "Block size", {"of"});
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    catch (args::ValidationError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    std::cout << "bs = " << args::get(bs) << std::endl;
    std::cout << "skip = " << args::get(skip) << std::endl;
    if (input) { std::cout << "if = " << args::get(input) << std::endl; }
    if (output) { std::cout << "of = " << args::get(output) << std::endl; }
    return 0;
}
 % ./test help
  ./test {OPTIONS}

    This command likes to break your disks

  OPTIONS:

      help                              Show this help menu.
      bs=[BYTES]                        Block size
      skip=[BYTES]                      Bytes to skip
      if=[BLOCK SIZE]                   Block size
      of=[BLOCK SIZE]                   Block size

 % ./test bs=1024 skip=7 if=/tmp/input
bs = 1024
skip = 7
if = /tmp/input

Windows style

The code is the same as above, but the two lines are replaced out:

parser.LongPrefix("/");
parser.LongSeparator(":");
 % ./test /help     
  ./test {OPTIONS}

    This command likes to break your disks

  OPTIONS:

      /help                             Show this help menu.
      /bs:[BYTES]                       Block size
      /skip:[BYTES]                     Bytes to skip
      /if:[BLOCK SIZE]                  Block size
      /of:[BLOCK SIZE]                  Block size

 % ./test /bs:72 /skip:87 /if:/tmp/test.txt
bs = 72
skip = 87
if = /tmp/test.txt
 % 

Group nesting help menu text

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::Group xorgroup(parser, "this group provides xor validation:", args::Group::Validators::Xor);
    args::Flag a(xorgroup, "a", "test flag", {'a'});
    args::Flag b(xorgroup, "b", "test flag", {'b'});
    args::Flag c(xorgroup, "c", "test flag", {'c'});
    args::Group nxor(xorgroup, "this group provides all-or-none (nxor) validation:", args::Group::Validators::AllOrNone);
    args::Flag d(nxor, "d", "test flag", {'d'});
    args::Flag e(nxor, "e", "test flag", {'e'});
    args::Flag f(nxor, "f", "test flag", {'f'});
    args::Group nxor2(nxor, "this group provides all-or-none (nxor2) validation:", args::Group::Validators::AllOrNone);
    args::Flag i(nxor2, "i", "test flag", {'i'});
    args::Flag j(nxor2, "j", "test flag", {'j'});
    args::Flag k(nxor2, "k", "test flag", {'k'});
    args::Group nxor3(nxor, "this group provides all-or-none (nxor3) validation:", args::Group::Validators::AllOrNone);
    args::Flag l(nxor3, "l", "test flag", {'l'});
    args::Flag m(nxor3, "m", "test flag", {'m'});
    args::Flag n(nxor3, "n", "test flag", {'n'});
    args::Group atleastone(xorgroup, "this group provides at-least-one validation:", args::Group::Validators::AtLeastOne);
    args::Flag g(atleastone, "g", "test flag", {'g'});
    args::Flag o(atleastone, "o", "test flag", {'o'});
    args::HelpFlag help(parser, "help", "Show this help menu", {'h', "help"});
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        parser.Help(std::cerr);
        return 1;
    }
    catch (args::ValidationError e)
    {
        std::cerr << e.what() << std::endl;
        parser.Help(std::cerr);
        return 1;
    }
    return 0;
}
 % /tmp/test -h
  /tmp/test {OPTIONS} 

    This is a test program. 

  OPTIONS:

                         this group provides xor validation: 
        -a                 test flag 
        -b                 test flag 
        -c                 test flag 
                           this group provides all-or-none (nxor) validation: 
          -d                 test flag 
          -e                 test flag 
          -f                 test flag 
                             this group provides all-or-none (nxor2) validation:
            -i                 test flag 
            -j                 test flag 
            -k                 test flag 
                             this group provides all-or-none (nxor3) validation:
            -l                 test flag 
            -m                 test flag 
            -n                 test flag 
                           this group provides at-least-one validation: 
          -g                 test flag 
          -o                 test flag 
      -h, --help         Show this help menu 

    This goes after the options. 
 %                                                                                

Mapping arguments

I haven't written out a long example for this, but here's the test case you should be able to discern the meaning from:

bool ToLowerReader(const std::string &name, const std::string &value, std::string &destination)
{
    destination = value;
    std::transform(destination.begin(), destination.end(), destination.begin(), ::tolower);
    return true;
}

TEST_CASE("Mapping types work as needed", "[args]")
{
    std::unordered_map<std::string, MappingEnum> map{
        {"default", MappingEnum::def},
        {"foo", MappingEnum::foo},
        {"bar", MappingEnum::bar},
        {"red", MappingEnum::red},
        {"yellow", MappingEnum::yellow},
        {"green", MappingEnum::green}};
    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::MapFlag<std::string, MappingEnum> dmf(parser, "DMF", "Maps string to an enum", {"dmf"}, map);
    args::MapFlag<std::string, MappingEnum> mf(parser, "MF", "Maps string to an enum", {"mf"}, map);
    args::MapFlag<std::string, MappingEnum, ToLowerReader> cimf(parser, "CIMF", "Maps string to an enum case-insensitively", {"cimf"}, map);
    args::MapFlagList<std::string, MappingEnum> mfl(parser, "MFL", "Maps string to an enum list", {"mfl"}, map);
    args::MapPositional<std::string, MappingEnum> mp(parser, "MP", "Maps string to an enum", map);
    args::MapPositionalList<std::string, MappingEnum> mpl(parser, "MPL", "Maps string to an enum list", map);
    parser.ParseArgs(std::vector<std::string>{"--mf=red", "--cimf=YeLLoW", "--mfl=bar", "foo", "--mfl=green", "red", "--mfl", "bar", "default"});
    REQUIRE_FALSE(dmf);
    REQUIRE(args::get(dmf) == MappingEnum::def);
    REQUIRE(mf);
    REQUIRE(args::get(mf) == MappingEnum::red);
    REQUIRE(cimf);
    REQUIRE(args::get(cimf) == MappingEnum::yellow);
    REQUIRE(mfl);
    REQUIRE((args::get(mfl) == std::vector<MappingEnum>{MappingEnum::bar, MappingEnum::green, MappingEnum::bar}));
    REQUIRE(mp);
    REQUIRE((args::get(mp) == MappingEnum::foo));
    REQUIRE(mpl);
    REQUIRE((args::get(mpl) == std::vector<MappingEnum>{MappingEnum::red, MappingEnum::def}));
    REQUIRE_THROWS_AS(parser.ParseArgs(std::vector<std::string>{"--mf=YeLLoW"}), args::MapError);
}

How fast is it?

This should not really be a question you ask when you are looking for an argument-parsing library, but every test I've done shows args as being about 65% faster than TCLAP and 220% faster than boost::program_options.

The simplest benchmark I threw together is the following one, which parses the command line -i 7 -c a 2.7 --char b 8.4 -c c 8.8 --char d with a parser that parses -i as an int, -c as a list of chars, and the positional parameters as a list of doubles (the command line was originally much more complex, but TCLAP's limitations made me trim it down so I could use a common command line across all libraries. I also have to copy in the arguments list with every run, because TCLAP permutes its argument list as it runs (and comparison would have been unfair without comparing all about equally), but that surprisingly didn't affect much. Also tested is pulling the arguments out, but that was fast compared to parsing, as would be expected.

The run:

% g++ -obench bench.cxx -O2 -std=c++11 -lboost_program_options
% ./bench
args seconds to run: 0.895472
tclap seconds to run: 1.45001
boost::program_options seconds to run: 1.98972
%

The benchmark:

#undef NDEBUG
#include <iostream>
#include <chrono>
#include <cassert>
#include "args.hxx"
#include <tclap/CmdLine.h>
#include <boost/program_options.hpp>
namespace po = boost::program_options;
using namespace std::chrono;
inline bool doubleequals(const double a, const double b)
{
    static const double delta = 0.0001;
    const double diff = a - b;
    return diff < delta && diff > -delta;
}
int main()
{
    const std::vector<std::string> carguments({"-i", "7", "-c", "a", "2.7", "--char", "b", "8.4", "-c", "c", "8.8", "--char", "d"});
    const std::vector<std::string> pcarguments({"progname", "-i", "7", "-c", "a", "2.7", "--char", "b", "8.4", "-c", "c", "8.8", "--char", "d"});
    // args
    {
        high_resolution_clock::time_point start = high_resolution_clock::now();
        for (unsigned int x = 0; x < 100000; ++x)
        {
            std::vector<std::string> arguments(carguments);
            args::ArgumentParser parser("This is a test program.", "This goes after the options.");
            args::ValueFlag<int> integer(parser, "integer", "The integer flag", {'i', "int"});
            args::ValueFlagList<char> characters(parser, "characters", "The character flag", {'c', "char"});
            args::PositionalList<double> numbers(parser, "numbers", "The numbers position list");
            parser.ParseArgs(arguments);
            const int i = args::get(integer);
            const std::vector<char> c(args::get(characters));
            const std::vector<double> n(args::get(numbers));
            assert(i == 7);
            assert(c[0] == 'a');
            assert(c[1] == 'b');
            assert(c[2] == 'c');
            assert(c[3] == 'd');
            assert(doubleequals(n[0], 2.7));
            assert(doubleequals(n[1], 8.4));
            assert(doubleequals(n[2], 8.8));
        }
        high_resolution_clock::duration runtime = high_resolution_clock::now() - start;
        std::cout << "args seconds to run: " << duration_cast<duration<double>>(runtime).count() << std::endl;
    }
    // tclap
    {
        high_resolution_clock::time_point start = high_resolution_clock::now();
        for (unsigned int x = 0; x < 100000; ++x)
        {
            std::vector<std::string> arguments(pcarguments);
            TCLAP::CmdLine cmd("Command description message", ' ', "0.9");
            TCLAP::ValueArg<int> integer("i", "int", "The integer flag", false, 0, "integer", cmd);
            TCLAP::MultiArg<char> characters("c", "char", "The character flag", false, "characters", cmd);
            TCLAP::UnlabeledMultiArg<double> numbers("numbers", "The numbers position list", false, "foo", cmd, false);
            cmd.parse(arguments);
            const int i = integer.getValue();
            const std::vector<char> c(characters.getValue());
            const std::vector<double> n(numbers.getValue());
            assert(i == 7);
            assert(c[0] == 'a');
            assert(c[1] == 'b');
            assert(c[2] == 'c');
            assert(c[3] == 'd');
            assert(doubleequals(n[0], 2.7));
            assert(doubleequals(n[1], 8.4));
            assert(doubleequals(n[2], 8.8));
        }
        high_resolution_clock::duration runtime = high_resolution_clock::now() - start;
        std::cout << "tclap seconds to run: " << duration_cast<duration<double>>(runtime).count() << std::endl;
    }
    // boost::program_options
    {
        high_resolution_clock::time_point start = high_resolution_clock::now();
        for (unsigned int x = 0; x < 100000; ++x)
        {
            std::vector<std::string> arguments(carguments);
            po::options_description desc("This is a test program.");
            desc.add_options()
                ("int,i", po::value<int>(), "The integer flag")
                ("char,c", po::value<std::vector<char>>(), "The character flag")
                ("numbers", po::value<std::vector<double>>(), "The numbers flag");
            po::positional_options_description p;
            p.add("numbers", -1);
            po::variables_map vm;
            po::store(po::command_line_parser(carguments).options(desc).positional(p).run(), vm);
            const int i = vm["int"].as<int>();
            const std::vector<char> c(vm["char"].as<std::vector<char>>());
            const std::vector<double> n(vm["numbers"].as<std::vector<double>>());
            assert(i == 7);
            assert(c[0] == 'a');
            assert(c[1] == 'b');
            assert(c[2] == 'c');
            assert(c[3] == 'd');
            assert(doubleequals(n[0], 2.7));
            assert(doubleequals(n[1], 8.4));
            assert(doubleequals(n[2], 8.8));
        }
        high_resolution_clock::duration runtime = high_resolution_clock::now() - start;
        std::cout << "boost::program_options seconds to run: " << duration_cast<duration<double>>(runtime).count() << std::endl;
    }
    return 0;
}

So, on top of being more flexible, smaller, and easier to read, it is faster than the most common alternatives.

args's People

Contributors

arthursonzogni avatar bitc avatar darealshinji avatar dhmemi avatar iamthebot avatar ivan-v-kush avatar kolanich avatar mapaydar avatar milipili avatar mtnviewjohn avatar nbdy avatar njlr avatar olivierldff avatar pysco68 avatar rholais avatar scotthutchinson avatar travisdowns avatar zhihaoy avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

args's Issues

Only the First Element of ValueFlagList gets parsed.

As the title says, only the first element of ValueFlagList seems to get parsed, see the reproducer below.

% g++ ValueFlagTest.cxx -g
% ./a.out --www more than one word
terminate called after throwing an instance of 'args::ParseError'
  what():  Passed in argument, but no positional arguments were ready to receive it: than
zsh: abort (core dumped)  ./a.out --www more than one word

I looked into and it seems that only a single word is given to ValueFlagList::ParseValues:

% gdb --args a.out -w eins zwei drei
gdb) b args.hxx:3621
Breakpoint 1 at 0x429904: file args.hxx, line 3621.
(gdb) run
Starting program: /home/jonas/valueflagtest/a.out -w eins zwei drei
Missing separate debuginfos, use: dnf debuginfo-install glibc-2.31-2.fc32.x86_64

Breakpoint 1, args::ValueFlagList<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, args::detail::vector, args::ValueReader>::ParseValue (this=0x7fffffffd210, 
    values_=std::vector of length 1, capacity 1 = {...}) at args.hxx:3621
3621	                values.insert(std::end(values), v);
Missing separate debuginfos, use: dnf debuginfo-install libgcc-10.1.1-1.fc32.x86_64 libstdc++-10.1.1-1.fc32.x86_64
(gdb) p values
$1 = std::vector of length 0, capacity 0
(gdb) p values_
$2 = std::vector of length 1, capacity 1 = {"eins"}

shouldn't values_ contain {"eins", "zwei", "drei"}?

Reproducer:

#include <iostream>

#include "args.hxx"

int main(int argc, char* argv[]) {
  args::ArgumentParser parser("Test of the ValueFlagList class");
  args::ValueFlagList<std::string> words(parser, "words", "words words words...", {'w', "www"});
  args::HelpFlag help(parser, "help", "show this help and exit", {'h', "help"});

  try {
    parser.ParseCLI(argc, argv);
  } catch (args::Help&) {
    std::cerr << parser << std::endl;
    return 0;
  }

  for (const auto& word : words) {
    std::cout << word << std::endl;
  }

  return 0;

}

include guards

Including the header multiple times results in redefinition warnings. Can we add either a #pragma once at the top or use a standard include guard? Can submit a PR if necesary but it's a one-liner.

Edit: definitely not a one liner. What's the point of the different test namespace abusing macros like that?

Disallow multiple arguments for a the same value flag

args::ValueFlag<int> integer(parser, "integer", "The integer flag", {'i'});
./program -i4 -i5

In this example the value at integer is set to 5. How can I make it an error to disallow such behaviour? I.e. only allow the -i flag to be passed once. Same issue with args::Flag too.

Multiple definitions during link

Hi!
Using the header from multiple source files results in link errors. Are the missing inline statements on purpose or by accident? Great library, thanks for it!

Memory Corruption with clang-cl

Hi,

I've encountered a weird bug when using args with clang-cl on Windows, in release mode only. Using Visual Studio 2019 debugger, I suspect a memory corruption. Here is the code:

#include "args.hpp"

#include <iostream>

inline auto to_argv(std::vector<std::string>& v)
{
	auto r = std::vector<char*>{};
	for (auto& e : v)
		r.emplace_back(e.data());
	r.emplace_back(nullptr);
	return r;
}

auto other_main(int argc, char* argv[]) -> int
{
	std::cerr << argc << std::endl;
	for(auto i = 0; i < argc; ++i)
		std::cerr << argv[i] << std::endl;
	auto parser = args::ArgumentParser{ "Command Line" };
	auto const help = args::HelpFlag{ parser, "help", "Display this help menu", {'h', "help"} };
	try
	{
		parser.ParseCLI(argc, argv);
	}
	catch (const args::Help&)
	{
	}
	return 0;
}

int main(int argc, char* argv[])
{
	auto const commands = std::vector<std::string>
	{
		"command",
		"command_2",
	};
	for (auto const& command : commands)
	{
		auto _args = std::vector<std::string>
		{
			command,
			"-h",
		};
		for (auto const& a : _args)
			std::cerr << a << std::endl;
		auto args = to_argv(_args);
		other_main(static_cast<int>(args.size()) - 1, args.data());
	}
}

This should print:

command
-h
2
command
-h
command_2
-h
2
command_2
-h

which it does in debug (or with MSVC or clang on Linux), but it prints:

command
-h
2
command
-h
command_2

2
command_2
-h

In other cases I tested, it prints rubbish, or simply crashes. I attached the whole self-contained sample, with example cmake commands.
args_bug.zip

No way to get parse error message in ARGS_NOEXCEPT mode

When using this library in ARGS_NOEXCEPT mode, there is no way to get the detailed error message.

When the user enters an incorrect command line, then the best we can do is print "Parse Error", instead of the more detailed parse error message.

Conditional args ?

Depending on a parent option value, is it possible to make children options required or not? (other than by adding additional checks after ArgumentParser::ParseCLI)

excluding options

Is it possible to make some options exclude or exclusive to each other and otherwise throw an exception?

For example --now can only be used if --open or --close was given and --open and --close cannot be used together.

Use of uninitialised value (allowJoinedLongValue)

There is a circular reference with allowJoinedLongValue and longseparator attributes in methods LongSeparator and SetArgumentSeparations (both called by ArgumentParser constructor).

LongSeparator uses allowJoinedLongValue (not initialized at this point), and allowJoinedLongValue is initialized only in SetArgumentSeparations (but it uses longseparator initialized in the previous method).

I've seen this using Valgrind. This is the Valgrind's output (PS: it's not the current args.hxx version but the problem is still there):
==22686== Conditional jump or move depends on uninitialised value(s)
==22686== at 0x414E4D: args::ArgumentParser::LongSeparator(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) (args.hxx:2097)
==22686== by 0x414AA6: args::ArgumentParser::ArgumentParser(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) (args.hxx:2040)
==22686== by 0x408CB3: main (myclass.cpp:1095)
==22686== Uninitialised value was created by a stack allocation
==22686== at 0x408C17: main (myclass.cpp:1094)

Prefix and postfix text in command usage string

Enable the ability to add additional text before and after usage text.
Currently, my master argument parser looks like this.

 prog {OPTIONS} [COMMAND]

I would like it to look like this

 prog {OPTIONS} [COMMAND] [<args>]

even tho the [<args>] bit is not backed up by any args from the master parser.

When the command parser gets a --help, i want the usage text to say

prog COMMAND {OPTIONS} [X] [Y] ......

This requires the disabling of the auto-appended argv[0] argument, and replace it with a string of my choice.

spdlog_ex's can throw exception

You should not store std::string in the spdlog_ex class, because the std::move in the constructor can throw an exception and also rethrowing the spdlog_ex exception will try to copy the _msg which can also throw an exception.

Using Windows like "/" short prefixes don't work

When trying to use Windows like "/" short prefixes via "parser.ShortPrefix("/")" such short options don't work or can't be matched. Using this kind of flags or value flags for short options ( /h /v /i ... etc.) don't work:

> test.exe /h
Flag could not be matched: h
  test.exe {OPTIONS}

    This is a test program.

  OPTIONS:

      /h, /help                         display this help section
      /v, /version                     show the program version
      /longopt                         use longopt opt
      * Required arguments: *
      /i[file], /input:[file]           the input file to deal with
      /o[file], /output:[file]       the resulting output file

These also don't work: /i [file] /o [file]

Further I think if such Windows like setable short options "/" would work, they would at least for short value flags /x:[value], also probably need to offer a setable short seperator ":" in order to be somehow slightly more Windows conform and distinguishable as an short flag with a value argument.

get full original command line (full argv[]) within a command function

Is there currently an easy way to pull out the full original command line string that was used to invoke the program (essentially what argv was) from within a Command/subparser with the current API? I use the commands interface, and have a separate function that is invoked for subcommands. Within a subcommand, I want to be able to get the full command line to be able to print it out to a log file that gets created based on the input args to the program. Is there a way to do this right now that I'm just missing?

Sub arguments (git like)

How to share flag with several flags?
Let's say I have Add and Init which except array of strings how can I declare it in one place and reuse it in Add or in Init

Thank you

Add macros to get version

args.hxx is missing a macro like ARGS_VERSION to get the version at compile time. A triplet ARGS_VERSION_MAJOR, ARGS_VERSION_MINOR and ARGS_VERSION_PATCH could be even better.

It could be useful for logs, for example.

Get position of matched argument

I am looking to implement a command based utility, which will use a master args parser
and then delegate the remaining arguments to a sub-parser.

The project states that it will never support flag arguments sensitive to order.

My use-case is as follows:
./prog --help
shall display the master arg parser help.

./prog COMMAND --help
should show the COMMAND arg parser help.
Since it appears it will not be a goal to support positional/conditional flag arguments,
I suggest adding an index position on the detected argument. That way, I can do the following:

catch (args::Help)
{
  if (command && args::position (help) > args::position (command))
    continue;

  ...
}

and thus delegate further processing to the command handler.

Nargs support

I see some Nargs class in the code, but not the documentation. Is it supported / maintained?

Required Flags

Hi,

Is there a simple way to mark things as required or mandatory? I've seen #4, but putting required flags in a group is OK, except, as you point out, the error message is not ideal.

SIGSEGV with args::ArgumentParser inside a class

Hi, i'm getting a SIGSEGV when calling args::ArgumentParser::ParseCLI().
Context:
args::ArgumentParser is a private member of some class.
An instance of args::HelpFlag is created on the constructor body, and the instance of args::ArgumentParser is passed as first parameter.
The crash occurs when I call args::ArgumentParser::ParseCLI() from the args::ArgumentParser instance in another function.

The following snippet should reproduce the problem:

#include "args.hxx"


class MyClass{
args::ArgumentParser parser;

public:	
	MyClass(const char* description = "A description", 
			const char* notes = "Some notes"):
		parser(description, notes)
	{
		args::HelpFlag help(parser, "help", "lala", {'h', "help"}); 
		//If I comment out the previous line the problem dissapears
	}

	void operator()(int argc, const char **argv){
		parser.ParseCLI(argc, argv);
	
	}


};

int main(int argc, const char *argv[])
{
	MyClass myobj; 
 	
	myobj(argc, argv); //SIGSEGV!!
	return 0;
}

and here's a dump of (part of) the Valgrind output:

==18241==    at 0x405446: args::Group::Reset() (in /tmp/X/test/using_args)
==18241==    by 0x4092E0: __gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > args::ArgumentParser::ParseArgs<__gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > >(__gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >, __gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >) (in /tmp/X/test/using_args)
==18241==    by 0x40774A: decltype (begin({parm#1})) args::ArgumentParser::ParseArgs<std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > >(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) (in /tmp/X/test/using_args)
==18241==    by 0x405A3E: args::ArgumentParser::ParseCLI(int, char const* const*) (in /tmp/X/test/using_args)
==18241==    by 0x40627D: MyClass::operator()(int, char const**) (in /tmp/X/test/using_args)
==18241==    by 0x402BC4: main (in /tmp/X/test/using_args)
==18241==  Address 0x28 is not stack'd, malloc'd or (recently) free'd
==18241== 
==18241== 
==18241== Process terminating with default action of signal 11 (SIGSEGV)
==18241==  Access not within mapped region at address 0x28

Better value parsing

Two general parsing issues that should be easy to address:

  1. "7" and " 7" parse as valid integers but "7 " and " 7 " do not.
  2. there are many string-like things besides std::string that have space breaking extraction problems, such as std::filesystem::path.

This is how I did it in dimcli:

template <typename T> 
bool Cli::stringTo(T & out, const std::string & src) const {
    // versions of stringTo_impl taking ints as extra parameters are
    // preferred (better conversion from 0), if they don't exist for T 
    // (because no out=src assignment operator exists) then the versions 
    // taking longs are considered.
    return stringTo_impl(out, src, 0, 0);
}

template <typename T>
auto Cli::stringTo_impl(T & out, const std::string & src, int, int) const
    -> decltype(out = src, bool()) 
{
    out = src;
    return true;
}

template <typename T>
auto Cli::stringTo_impl(T & out, const std::string & src, int, long) const
    -> decltype(std::declval<std::istringstream &>() >> out, bool()) 
{
    m_interpreter.clear();
    m_interpreter.str(src);
    if (!(m_interpreter >> out) || !(m_interpreter >> std::ws).eof()) {
        out = {};
        return false;
    }
    return true;
}

template <typename T>
bool Cli::stringTo_impl(
    T & /* out */, const std::string & /* src */, long, long
) const {
    // In order to parse an argument there must be one of:
    //  - assignment operator for std::string to T
    //  - istream extraction operator for T
    //  - parse action attached to the Opt<T> instance that doesn't call
    //    opt.parseValue(), such as opt.choice().
    assert(false && "no assignment from string or stream extraction operator");
    return false;
}

-Wunused-parameter warnings

A small request from me.
It'd be nice if args.hxx didn't generate warnings about unused parameters.

Ideally, it'd also avoid -Wshadow warnings, but this option is probably not that popular.

$ g++-6 -Wall -Wextra test.cxx -I.
In file included from test.cxx:16:0:
./args.hxx: In member function ‘virtual std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > args::Base::GetDescription(const string&, const string&, const string&, const string&) const’:
./args.hxx:400:92: warning: unused parameter ‘shortPrefix’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                            ^~~~~~~~~~~
./args.hxx:400:124: warning: unused parameter ‘longPrefix’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                                                            ^~~~~~~~~~
./args.hxx:400:155: warning: unused parameter ‘shortSeparator’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                                                                                           ^~~~~~~~~~~~~~
./args.hxx:400:190: warning: unused parameter ‘longSeparator’ [-Wunused-parameter]
  virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                                                                                                                   ^~~~~~~~~~~~~
./args.hxx: In member function ‘virtual std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > args::NamedBase::GetDescription(const string&, const string&, const string&, const string&) const’:
./args.hxx:436:92: warning: unused parameter ‘shortPrefix’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                            ^~~~~~~~~~~
./args.hxx:436:124: warning: unused parameter ‘longPrefi’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                            ^~~~~~~~~
./args.hxx:436:154: warning: unused parameter ‘shortSeparator’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                          ^~~~~~~~~~~~~~
./args.hxx:436:189: warning: unused parameter ‘longSeparator’ [-Wunused-parameter]
   virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                                                   ^~~~~~~~~~~~~
./args.hxx: In member function ‘virtual std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > args::FlagBase::GetDescription(const string&, const string&, const string&, const string&) const’:
./args.hxx:516:155: warning: unused parameter ‘shortSeparator’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                           ^~~~~~~~~~~~~~
./args.hxx:516:190: warning: unused parameter ‘longSeparator’ [-Wunused-parameter]
  virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                                                   ^~~~~~~~~~~~~
./args.hxx: In static member function ‘static bool args::Group::Validators::DontCare(const args::Group&)’:
./args.hxx:636:51: warning: unused parameter ‘group’ [-Wunused-parameter]
                 static bool DontCare(const Group &group)
                                                   ^~~~~
./args.hxx: In static member function ‘static bool args::Group::Validators::CareTooMuch(const args::Group&)’:
./args.hxx:641:54: warning: unused parameter ‘group’ [-Wunused-parameter]
                 static bool CareTooMuch(const Group &group)
                                                      ^~~~~
In file included from test.cxx:16:0:
./args.hxx: In member function ‘bool args::ValueReader<std::__cxx11::basic_string<char> >::operator()(const string&, const string&, std::__cxx11::string&)’:
./args.hxx:1567:44: warning: unused parameter ‘name’ [-Wunused-parameter]
         bool operator()(const std::string &name, const std::string &value, std::string &destination)
                                            ^~~~
test.cxx: In member function ‘void DoublesReader::operator()(const string&, const string&, std::tuple<double, double>&)’:
test.cxx:297:40: warning: unused parameter ‘name’ [-Wunused-parameter]
     void operator()(const std::string &name, const std::string &value, std::tuple<double, double> &destination)
                                        ^~~~
test.cxx: In member function ‘void ToLowerReader::operator()(const string&, const string&, std::__cxx11::string&)’:
test.cxx:424:40: warning: unused parameter ‘name’ [-Wunused-parameter]
     void operator()(const std::string &name, const std::string &value, std::string &destination)
                                        ^~~~
In file included from test.cxx:576:0:
./args.hxx: In member function ‘virtual std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > argstest::Base::GetDescription(const string&, const string&, const string&, const string&) const’:
./args.hxx:400:92: warning: unused parameter ‘shortPrefix’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                            ^~~~~~~~~~~
./args.hxx:400:124: warning: unused parameter ‘longPrefix’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                                                            ^~~~~~~~~~
./args.hxx:400:155: warning: unused parameter ‘shortSeparator’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                                                                                           ^~~~~~~~~~~~~~
./args.hxx:400:190: warning: unused parameter ‘longSeparator’ [-Wunused-parameter]
  virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const
                                                                                                                                                                                   ^~~~~~~~~~~~~
./args.hxx: In member function ‘virtual std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > argstest::NamedBase::GetDescription(const string&, const string&, const string&, const string&) const’:
./args.hxx:436:92: warning: unused parameter ‘shortPrefix’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                            ^~~~~~~~~~~
./args.hxx:436:124: warning: unused parameter ‘longPrefi’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                            ^~~~~~~~~
./args.hxx:436:154: warning: unused parameter ‘shortSeparator’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                          ^~~~~~~~~~~~~~
./args.hxx:436:189: warning: unused parameter ‘longSeparator’ [-Wunused-parameter]
   virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefi, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                                                   ^~~~~~~~~~~~~
./args.hxx: In member function ‘virtual std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > argstest::FlagBase::GetDescription(const string&, const string&, const string&, const string&) const’:
./args.hxx:516:155: warning: unused parameter ‘shortSeparator’ [-Wunused-parameter]
             virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                           ^~~~~~~~~~~~~~
./args.hxx:516:190: warning: unused parameter ‘longSeparator’ [-Wunused-parameter]
  virtual std::tuple<std::string, std::string> GetDescription(const std::string &shortPrefix, const std::string &longPrefix, const std::string &shortSeparator, const std::string &longSeparator) const override
                                                                                                                                                                                   ^~~~~~~~~~~~~
./args.hxx: In static member function ‘static bool argstest::Group::Validators::DontCare(const argstest::Group&)’:
./args.hxx:636:51: warning: unused parameter ‘group’ [-Wunused-parameter]
                 static bool DontCare(const Group &group)
                                                   ^~~~~
./args.hxx: In static member function ‘static bool argstest::Group::Validators::CareTooMuch(const argstest::Group&)’:
./args.hxx:641:54: warning: unused parameter ‘group’ [-Wunused-parameter]
                 static bool CareTooMuch(const Group &group)
                                                      ^~~~~
In file included from test.cxx:576:0:
./args.hxx: In member function ‘bool argstest::ValueReader<std::__cxx11::basic_string<char> >::operator()(const string&, const string&, std::__cxx11::string&)’:
./args.hxx:1567:44: warning: unused parameter ‘name’ [-Wunused-parameter]
         bool operator()(const std::string &name, const std::string &value, std::string &destination)
                                            ^~~~
./args.hxx: In instantiation of ‘bool argstest::ValueReader<T>::operator()(const string&, const string&, T&) [with T = int; std::__cxx11::string = std::__cxx11::basic_string<char>]’:
./args.hxx:1600:21:   required from ‘void argstest::ValueFlag<T, Reader>::ParseValue(const string&) [with T = int; Reader = argstest::ValueReader<int>; std::__cxx11::string = std::__cxx11::basic_string<char>]’
test.cxx:635:1:   required from here
./args.hxx:1540:45: warning: unused parameter ‘name’ [-Wunused-parameter]
         bool operator ()(const std::string &name, const std::string &value, T &destination)

Group validation doesn't work in Subparser

#include <iostream>
#include <args.hxx>

int main(int argc, char **argv) {
  args::ArgumentParser parser("This is a test program.");
  args::HelpFlag help(parser, "help", "Display this help menu", {'h', "help"});
  args::Group commands(parser, "commands");

  args::Command solve(
      commands, "solve", "you know", [&](args::Subparser &parser) {
        args::Group required(parser, "", args::Group::Validators::All);
        args::Positional<std::string> file(required, "file",
                                           "This file is required");
        parser.Parse();
        std::cout << "File input: " << args::get(file) << std::endl;
      });
  try {
    parser.ParseCLI(argc, argv);
  } catch (args::Help) {
    std::cout << parser;
    return 0;
  } catch (args::Error e) {
    std::cerr << e.what() << std::endl;
    std::cerr << parser;
    return 1;
  }
  return 0;
}

a.exe solve
File input:
^ empty string

I have workaround because I only have one positional flag, so I can use args::Options::Required, but still want to know whether this should work.

Getting a Map as parse result

Is there a way to get a Map or List<pair> with the parsed values so that you can use it in another class to process the params..?

I can't find it..

Implicit values

It would be nice to have implicit values for flags like -j[N] in make.

I know they are mentioned in readme:

It will not ever:

  • Allow one value flag to take a specific number of values (like --foo first second, where --foo slurps both arguments). You can instead split that with a flag list (--foo first --foo second) or a custom type extraction ( --foo first,second)
  • Allow you to have value flags only optionally accept values

Is it because of the technical difficulties? I have working implementation, but it requires some incompatible changes in interfaces (ValueFlagBase::ParseValue for instance). Usage is simple:

ImplicitValueFlag<int> foo("foo", "foo", implicitValue, defaultValue);
// or: ImplicitValueFlag<int> foo("foo", "foo", defaultValue);
// or: ImplicitValueFlag<int> foo("foo", "foo");

Will you accept such PR?

noexcept warning in Visual Studio 2019

This kind of function may not throw. Declare it 'noexcept' (f.6). 460

                Matcher(EitherFlag::GetShort(in), EitherFlag::GetLong(in)) {}

            Matcher(Matcher &&other) : shortFlags(std::move(other.shortFlags)), longFlags(std::move(other.longFlags))

Feature request: set those args which are matched to 0

In args::parse_args, rather than parsing const char** argv , parse char** argv and set those argv entries to null if they are matched.

Furthermore, in ParseCLI, only populate the std::vector<std::string> args vector with entries in argv which are not null.

With both suggestions, we can start nesting parsers. For example we parse a first set of flags, then go to the next set of flags depending on the result of the first parser, using the remaining non-null argv arguments.

Add possible values to help output for MapFlag

For MapFlag is it possible to get the list of possible values added to the help output? For example:

enum class Example {
  X,
  Y,
  Z
};
std::unordered_map<std::string, Example> exampleMapValues{
  {'thexoption', Example::X},
  {'theyoption', Example::Y},
  {'thezoption', Example::Z}
};
args::MapFlag<std::string, Example> exampleFlag(
  arguments, "mv", "A description", { 'm', "mapvalue" }, exampleMapValues);

Currently results in help output (for that option) of:

      -m[mv], --mapvalue=[mv]           A description

If the possible values could be automatically added to the help output, something along the lines of:

      -m[mv], --mapvalue=[mv]           A description
                                        One of: thexoption, theyoption, thezoption

Would save a lot of effort on behalf of users, and possible mistakes in forgetting to add/remove values. The information is already there as well, encoded in the unordered_map.

[GCC 8] error: catching polymorphic type by value

I ran into this problem while compiling my project with gcc 8 today.
myproject/args.hxx:1764:34: error: catching polymorphic type ‘class args::SubparserError’ by value [-Werror=catch-value=] catch (args::SubparserError) ^~~~~~~~~~~~~~
I compiled with the flag -Werror which triggered the error.

Positional arguments example fails

I am trying this README example:

// Argument flags, Positional arguments, lists

#include <iostream>
#include <args.hxx>
int main(int argc, char **argv)
{
    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::HelpFlag help(parser, "help", "Display this help menu", {'h', "help"});
    args::ValueFlag<int> integer(parser, "integer", "The integer flag", {'i'});
    args::ValueFlagList<char> characters(parser, "characters", "The character flag", {'c'});
    args::Positional<std::string> foo(parser, "foo", "The foo position");
    args::PositionalList<double> numbers(parser, "numbers", "The numbers position list");
    try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    catch (args::ValidationError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    if (integer) { std::cout << "i: " << args::get(integer) << std::endl; }
    if (characters) { for (const auto ch: args::get(characters)) { std::cout << "c: " << ch << std::endl; } }
    if (foo) { std::cout << "f: " << args::get(foo) << std::endl; }
    if (numbers) { for (const auto nm: args::get(numbers)) { std::cout << "n: " << nm << std::endl; } }
    return 0;
}

It prints:

# ./test -c x a b c d e
c: x
f: a
n: 0
n: 0
n: 0
n: 0

"n" is printed for double numbers and b c d e aren't numbers. Why does it print zeros for them?

Command parsing

Pretty often one app have many commands. And option flags set additional parameters to that command. For example:
git log --source
rails s -p 3131
or pod install --help

I found really good example of argument parsing library for Go, called Cobra: https://github.com/spf13/cobra Which solves this task with ease. Is there a chance that you decide to add similar command parsing into Args?

Wrapper for ARGS in a settings manager class

Hi,

I'm facing some issues trying to create a settings manager for my application based on ARGS (and I really love this library).

This is the code I'm working on (settingsmanager.h) :

#ifndef SETTINGSMANAGER_H
#define SETTINGSMANAGER_H

/*
 * Includes
 */
#include "args.hxx"
#include <unordered_map>

class SettingsManager
{
public:

    enum class eSetting {
        flagA,
        flabB,
        flagC,
        valueFlagA, // str
        valueFlagB // str
        valueFlagC // int
    };
    
    SettingsManager();
    ~SettingsManager(void);
    
    bool Initialize(int argc, char **argv);
    
    // -------
    // AWFUL CODE
            template<typename T>
    T get(eSetting setting) {
        switch(setting) {
            case eSetting::flagA:
            case eSetting::flagB:
            case eSetting::flagC:
            {
                args::Flag* flag = static_cast<args::Flag*>(*(settingsMap_.at(setting)));
                return args::get(*flag);
                break;
            }
            case eSetting::valueFlagA:
            case eSetting::valueFlagB:
            {
                args::ValueFlag<std::string>* flag = static_cast<args::ValueFlag<std::string>*>(*(settingsMap_.at(setting)));
                return args::get(*flag);
                break;
            {
            case eSetting::valueFlagC:
            {
                args::ValueFlag<int>* flag = static_cast<args::ValueFlag<int>*>(*(settingsMap_.at(setting)));
                return args::get(*flag);
                break;
            }
            default:
                return false;
                break;
        }
    }
    // ------
    
    /*
    // What kind of code I would like...
    template<typename T>
    T get(eSetting setting) {
        return args::get(*settingsMap.at(setting));
    }
    */
    
private:

    static args::ArgumentParser cliParser_;
    static args::Flag flagA_;
    static args::Flag flagB_;
    static args::Flag flagC_;
    static args::ValueFlag<std::string> valueFlagA_;
    static args::ValueFlag<std::string> valueFlagB_;
    static args::ValueFlag<int> valueFlagC_;

    std::unordered_map<eSetting, args::FlagBase*> settingsMap_;
};

#endif // SETTINGSMANAGER_H

I would like a generic get method that can return any type (string, int, double).
The rest of my app is supposed to know only the enum eSetting (not ARGS namespace).

Is it possible ? Which is the syntax for such template function ?
Should I review my conception to let ARGS management only in the main ?

Thx for help

Making it faster (although you shouldn't care)

I enjoyed your benchmark, and args was about ~15% faster than dimcli, but when I reduced the loop to just the parse call and asserts it was 30% slower. This is entirely because creating an istringstream object takes a long time, if you did something like make it a member of ValueReader and just call ss.clear(); ss.str(value); for each parse you'll go 20-40% faster overall - yes, it makes that much of a difference.

Unable to chain positional lists

Hi,

First, thanks for your great lib !

Unless i misunderstood usage, i did not find a way to chain positional lists as documented in "Long descriptions and proper wrapping and listing".

Indeed, the first positional list grab all next parameters event using the "--" delimiter.

Here is my code :

	args::ArgumentParser parser("This is a test program with a really long description that is probably going to have to be wrapped across multiple different lines.  This is a test to see how the line wrapping works", "This goes after the options.  This epilog is also long enough that it will have to be properly wrapped to display correctly on the screen");
	args::HelpFlag help(parser, "HELP", "Show this help menu.", { 'h', "help" });
	args::ValueFlag<std::string> foo(parser, "FOO", "The foo flag.", { 'a', 'b', 'c', "a", "b", "c", "the-foo-flag" });
	args::ValueFlag<std::string> bar(parser, "BAR", "The bar flag.  This one has a lot of options, and will need wrapping in the description, along with its long flag list.", { 'd', 'e', 'f', "d", "e", "f" });
	args::ValueFlag<std::string> baz(parser, "FOO", "The baz flag.  This one has a lot of options, and will need wrapping in the description, even with its short flag list.", { "baz" });
	args::Positional<std::string> pos1(parser, "POS1", "The pos1 argument.");
	args::PositionalList<std::string> poslist1(parser, "POSLIST1", "The poslist1 argument.");
	args::Positional<std::string> pos2(parser, "POS2", "The pos2 argument.");
	args::PositionalList<std::string> poslist2(parser, "POSLIST2", "The poslist2 argument.");

	parser.ParseArgs(std::vector<std::string>{"pos1", "foo", "bar", "--" , "pos2","baz"});

	auto a = args::get(pos1);
	auto b = args::get(poslist1);
	auto c = args::get(pos2);
	auto d = args::get(poslist2);

poslist1 contains now {"foo" ,"bar" , "pos2" , "baz"}

Cheers,
S.

Default arguments, ValueFlagList and reset

Hi,

when I initialize a ValueFlagList with default arguments these defaults are reset when parsing the arguments.
Is it possible to circumvent this?

Thanks in advance!

add copy constructors and/or move semantics to support modern C++ auto expresions

I'd love to write this:

    auto parser = args::ArgumentParser(
        "Benchmark a BFS graph search on a knureon complex"
    );

    auto help = args::HelpFlag(
        parser,
        "help",
        "Display this help menu",
        {'h', "help"}
    );

    auto args::ValueFlag<uint32_t>(
        parser,
        "seed",
        "The seed to initialize the random number generator",
        {"seed"}
    );

    auto scale = args::ValueFlag<uint32_t>(
        parser,
        "scale",
        "The logarithm base two of the number of vertices",
        {'s', "scale"}
    );

    auto edgefactor = args::ValueFlag<uint32_t>(
        parser,
        "edgefactor",
        "The ratio of the graph’s edge count to its vertex count",
        {'e', "edgefactor"}
    );

as I find it easier to read and encourages the use of auto everywhere.

Required positional argument

I read through the guide and couldn't find anything on required positional arguments. For example:

./program {OPTIONS} <file> 

Here <file> would be a positional argument that must appear somewhere in the arguments.

Parse known args but ignore unknown ones?

Can the following be achieved by this library?

In my main() function, I want to check against "some" arguments, namely -i thefile.img, but want to ignore others, namely --gtest-xyz, as the latter will later be parsed/extraced by GoogleTest.

While GoogleTest has it's own argument parsing code, I dislike to write my own argument parser for my main() function. What I could do is adding all GoogleTest specific arguments to the parser in my main function... but that seems a bit brittle, hence I'm looking for a better solution.

I'm totally aware that this is not the standard use case for argument parser libraries... nevertheless, my hope is that this library can help me with this. Maybe I could write my own Matcher? Any hints?

Q: How to setup an optional throwable version flag and other required group flags together...?

I somehow stumbled about the following here. - I wanted to have an optional -v | --version flag, just for printing out a program version, which works let's say similar like accessing the "-h | --help" output text mechanism (help exception output). and then exits the program.

But when I also define together a required group of value flags as to be "all" validated, a usual/normal optional flag like "-v" will never be executed, instead only always the text "Group validation failed somewhere!" output of the parser together with the help output is shown.

See this:

args::ArgumentParser parser("This is a test program.", "Example: test -i file -o file");
args::HelpFlag help(parser, "help", "display this help section", {'h', "help"});
args::Flag version(parser, "version", "show the program version", {'v', "version"});

args::Group filegroup(parser, "* Required arguments: *", args::Group::Validators::All);
args::ValueFlag<std::string> input(filegroup, "file", "the input file to deal with", {'i', "input"});
args::ValueFlag<std::string> output(filegroup, "file", "the resulting output file", {'o', "output"});

try
    {
        parser.ParseCLI(argc, argv);
    }
    catch (args::Help)
    {
        std::cout << parser;
        return 0;
    }
    catch (args::ParseError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    catch (args::ValidationError e)
    {
        std::cerr << e.what() << std::endl;
        std::cerr << parser;
        return 1;
    }
    if (version) { std::cout << " test v.1.0 - Copyright (c) 2017 by Testcorp" << std::endl; exit(0); }
    if (input) { inputFilename = args::get(atninput); }
    if (output) { outputFilename = args::get(atnoutput); }
    ...
    ...

Invoking the program with "./test -v" or "./test --version" gives always only

"Group validation failed somewhere!"
...help text...

So how would one handle an optional version flag setup, which behaves here like the "-h | --help" optional and allows to throw and print out just some message text and then exit, without giving out instead the parser group validation output ("Group validation failed somewhere!") together with the help text?

From where did you obtained catch.hpp

Hi,
I'm currently busy to package args for Debian since it is a precondition for some projects of the Debian Med team. The Debian ftpmaster has rejected the code since it is not clear how the file catch.hpp was generated. I've searched the internet for this file but had no real luck to find the source - just other instances of that file are used in several other projects.
So could you please enlighten me where to download the real source and how the file was generated?
Kind regards, Andreas.

Change name of the project

I assume you never expected this library to become so popular and just went with the most straight forward name. Unfortunately that makes it really hard to find community resources using search engines, because they see it as a generic programming keyword. Your username is really easy to recognize though, so maybe you can make that part of the project name.

However that's just a suggestion and there certainly are many arguments against a name change.

A way to exclude an option from help output

Is there any way to indicate that an option should be excluded from help output? Based on a quick scan of the code it seems like there isn't.

It is useful for "internal" flags that shouldn't be seen by the end user (for example, I have a script that launches the process with some internal flag set indicating that the process should return a value to the script, but an end-user shouldn't care about this flag).

The workaround I'm using now is to create a Group call with_help, a child of the real ArgumentParser and add arguments that should show help there, and internal arguments directly to the root parser, like this:

    args::ArgumentParser true_parser{"hidden-parser - this description won't show up anywhere"};
    args::Group with_help{parser};

    // public args
    args::HelpFlag help{with_help, "help", "Display this help menu", {'h', "help"}};
    args::Flag public_arg1{with_help, "public-arg1", "Help for arg1", {"arg1"}};
    args::Flag public_arg1{with_help, "public-arg1", "Help for arg1", {"arg1"}};

    // private args
    args::Flag public_arg1{true_parser, "hidden-arg1", "", {"hidden-arg1"}};

Now when I want to output I create a dummy/temporary new ArgumentParser and add the with_args child group to it:

    args::ArgumentParser help_parser("some-application: help goes here");
    help_parser.Add(with_help);
    std::cerr << help_parser;

Maybe that's already the best way?

Make help text "'--' can be used to terminate..." optional

The following help text entry is not optional if you have both options and arguments

      "--" can be used to terminate flag options and force all following
      arguments to be treated as positional options

The offending piece of code

if (hasoptions && hasarguments)
{
  for (const std::string &item: Wrap(std::string("\"") + terminator + "\" can be used to terminate flag options and force all following arguments to be treated as positional options", helpParams.width - helpParams.flagindent))
  {
    help << std::string(helpParams.flagindent, ' ') << item << '\n';
  }
}

Consider making this help text optional. (For my use-case, it is not possible to use. It just makes noise)

Allow inclusion into multiple source files

Currently you get a "multiple definition" error when linking two source files that include args.hxx. The affected functions are:

std::string::size_type Glyphs(const std::string &string_)
std::vector<std::string> Wrap(const std::string &in, const std::string::size_type width, std::string::size_type firstlinewidth = 0)
std::ostream &operator<<(std::ostream &os, const ArgumentParser &parser)

I resolved the error by making them inline or static, but I don't have much experience with header only libraries, so it may not be the best solution.

Sub group validation not working as expected

I've created a group and a subgroup which has an AllOrNone validator (see example below). I expect that I must specify either all -a -b -c flags or none as arguments. This is not the case. I can specify one or more.

cpp    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::Group group (parser, "Group:", args::Group::Validators::DontCare);
    args::Group subgroup (group, "SubGroup:", args::Group::Validators::AllOrNone);
    args::Flag aflag(subgroup, "a", "test flag", {'a'});
    args::Flag bflag(subgroup, "b", "test flag", {'b'});
    args::Flag cflag(subgroup, "c", "test flag", {'c'});

If I make the make the change below (set subgroup parent as parser), then it works. Is this a bug?

cpp    args::ArgumentParser parser("This is a test program.", "This goes after the options.");
    args::Group group (parse, "SubGroup:", args::Group::Validators::AllOrNone);
    args::Flag aflag(subgroup, "a", "test flag", {'a'});
    args::Flag bflag(subgroup, "b", "test flag", {'b'});
    args::Flag cflag(subgroup, "c", "test flag", {'c'});

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.