#BEYOND COMPARE COMMAND LINE WINDOWS#

Or can also bind parsers to lambdas for more custom handling.Bind parsers directly to variables that will receive the results of the parse - no intermediate dictionaries to worry about.Combine these to produce a composite parser - this can be done in stages across multiple function calls - or even projects. Each Opt or Arg is an independent parser. Define your interface once to get parsing, type conversions and usage strings with no redundancy.A single header file with no external dependencies (except the std library).The usage string is built from the information supplied and is formatted for the console width.Īs a convenience, the standard help options ( -h, -help and -?) can be specified using the Help parser,įor more usage please see the unit tests or look at how it is used in the Catch code-base ().įuller documentation will be coming soon. They otherwise work just like Opts.Ī, console optimised, usage string can be obtained by inserting the parser into a stream. That can be converted from a string using std::ostream.Īrgs specify arguments that are not tied to options, and so have no square bracket names. The first argument to an Opt is any variable, local, global member, of any type The option names are provided in one or more sets of square brackets, and a description string canīe provided in parentheses. Or they are pure flags (such as -d), in which case the Opt has only one argument - which must be a boolean. Options can be argument taking (such as -w 42), in which case the Opt takes a second argument - a hint,

#BEYOND COMPARE COMMAND LINE WINDOWS#

On Windows forward slashes are also accepted (and automatically interpretted as a short dash). Opts specify options that start with a short dash ( -) or long dash ( -).

Beyond compare command line