12 results (0.168 seconds)
++ed by:
ALEXBIO ARISTOTLE ARJONES BRUNOV DAGOLDEN

11 PAUSE user(s)
8 non-PAUSE user(s).

Ricardo SIGNES
Documentation
App::Cmd::Tutorial - getting started with App::Cmd
Modules
App::Cmd - write command line apps with less suffering
App::Cmd::ArgProcessor - App::Cmd-specific wrapper for Getopt::Long::Descriptive
App::Cmd::Command - a base class for App::Cmd commands
App::Cmd::Command::commands - list the application's commands
App::Cmd::Command::help - display a command's help screen
App::Cmd::Simple - a helper for building one-command App::Cmd applications
App::Cmd::Subdispatch - an App::Cmd::Command that is also an App::Cmd
App::Cmd::Subdispatch::DashedStyle - "app cmd --subcmd" style subdispatching
App::Cmd::Tester - for capturing the result of running an app
Provides
App::Cmd::Plugin in lib/App/Cmd/Plugin.pm
App::Cmd::Setup in lib/App/Cmd/Setup.pm
App::Cmd::Tester::Result in lib/App/Cmd/Tester.pm
Changes for version 0.300
    • DEPRECATED -run OPTION TO APP CLASS IMPORT
    • "use MyApp -run;" is deprecated; it will be removed after no less
    • than a year
    • this led to problems where normal exit-on-error messages confused
    • users by complaining about failing to compile; magic to stop this is
    • not worth the tiny savings
    • COMMANDS SHOULD NOW HAVE ->execute RATHER THAN ->run
    • this will not break you code... except:
    • WILL BREAK YOUR CODE: App::Cmd::Simple programs must use ->execute
    • rather than ->run



Hosting generously
sponsored by Bytemark