Abstract: The design, creation, use, and execution of command line parsers based on subcommand classes instead of boilerplate code is described. Commands and subcommands have corresponding class definitions, which upon instantiation based on command line content will provide and execute code to perform the command. Subcommand dispatching may be accomplished using delegates, using an interface implementation, or otherwise. Class attributes may define help text, argument aliases, and other metadata. Subcommand types may be passed as generic arguments, as objects, or otherwise. Arguments may be made optional or be required by providing or omitting class constructor parameter default values. By using classes to implement subcommands and avoiding reliance on large error-prone if or switch statements, parser development is made easier and more efficient.

Abstract: The design, creation, use, and execution of command line parsers based on subcommand classes instead of boilerplate code is described. Commands and subcommands have corresponding class definitions, which upon instantiation based on command line content will provide and execute code to perform the command. Subcommand dispatching may be accomplished using delegates, using an interface implementation, or otherwise. Class attributes may define help text, argument aliases, and other metadata. Subcommand types may be passed as generic arguments, as objects, or otherwise. Arguments may be made optional or be required by providing or omitting class constructor parameter default values. By using classes to implement subcommands and avoiding reliance on large error-prone if or switch statements, parser development is made easier and more efficient.