|0.1.15||Jul 11, 2019|
|0.1.14||Jul 11, 2019|
|0.1.13||Aug 25, 2018|
|0.1.6||Jul 31, 2018|
|0.0.2||Jul 7, 2018|
#52 in Command-line interface
143 downloads per month
Used in 2 crates
Parse command line arguments by defining a struct. It combines clap with custom derive.
The basic idea is that you define a type that represents the
information you want on the command-line from the person running your
derive(ClapMe) on that type, and then call
YourType::from_args() to find out what your user gave you.
ClapMe uses clap to do the actual parsing of command-line flags. This is great, because clap does an awesome job at providing helpful features you wouldn't even have thought of if you wrote your own command-line processor. The biggest downside to using clap directly is that it does not nicely support translating its results into something you would want to use in your code, so there is a fair amount of repetitious calling of macros to do conversions into useful types.
StructOpt is a tool that serves the same
function as clapme, but with a different philosophy. StructOpt
strives to be as expressive as clap, and to enable all features clap
does, and with a tightly coupled API. It does this by extensive use
of attributes such as
#[structopt(long = "long-name")], which define
the behavior and property of each flag. This makes it powerful, but
also rather verbose to use.
In contrast, ClapMe does not (yet?) support any attributes, and determines all behavior directly from your type. This means that you don't repeat yourself, but also means that you have less fine-grained control over your interface, and some interfaces may be well-nigh impossible.
You can implement the
ClapMe trait manually, which does make it
possible (and not even that painful) to create a different
command-line for a given type, but this is not the intended way to use
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.