document updated 10 years ago, on Oct 15, 2014

Options parsing for the command-line:

opts — uses PadWalker magic
Getopt::Std [in core as of v5.0]
Getopt::Long [in core as of v5.0]
Getopt::Compact
arguments are parsed in a totally standard way, with no custom per-argument rules, allowing the caller to specify an open-ended number of arguments (akin to %ENV, and even to XML/JSON in the way that it's unstructured)
- Getopt::Casual
auto-usage()
- Options
- Easy::Options
- Getopt::Lazy
- Getopt::Long::Descriptive
- Getopt::OO
- Getopt::Declare
- Getopt::Tiny
- Getopt::Tabular
- Getopt::Compact
- Getopt::Flex
- Getopt::GUI::Long
- Getopt::Tree
- Getopt::Mixed::Help
- Getopt::Fancy
- other random ways to do auto-usage(), that aren't quite the same as the above:
  - Pod::Usage
Getopt::Lucid — code that uses it is much easier to read for neophytes
Getopt::Attribute
Getopt::ll — flexible
Getopt::Modular
Getopt::Awesome
larger / more complex systems
- AppConfig — its options can be set via command-line, config-file, or CGI-parameters
- MooseX::Getopt
- firmly embedded in an app-framework
  - CLI::Application
  - App::Cmd
near arbitrary-complexity?
- Getopt::ExPar
command-line completion generators
- Getopt::Complete
- Getopt::Complete