The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.

Search results for "module:MooseX::Getopt::Basic"

MooseX::Getopt::Basic - MooseX::Getopt::Basic - role to implement the Getopt::Long functionality River stage three • 110 direct dependents • 325 total dependents

This is like MooseX::Getopt and can be used instead except that it doesn't make use of Getopt::Long::Descriptive (or "GLD" for short)....

ETHER/MooseX-Getopt-0.76 - 18 Dec 2023 20:20:08 UTC

MooseX::App - Write user-friendly command line apps with even less suffering River stage two • 32 direct dependents • 57 total dependents

MooseX-App is a highly customisable helper to write user-friendly command line applications without having to worry about most of the annoying things usually involved. Just take any existing Moose class, add a single line ("use MooseX-App qw(PluginA ...

MAROS/MooseX-App-1.43 - 21 Oct 2023 12:08:25 UTC

MooseX::Daemonize - Role for daemonizing your Moose based application River stage two • 9 direct dependents • 16 total dependents

Often you want to write a persistent daemon that has a pid file, and responds appropriately to Signals. This module provides a set of basic roles as an infrastructure to do that....

ETHER/MooseX-Daemonize-0.22 - 07 Dec 2019 01:26:55 UTC

MooseX::Getopt::Usage - Extend MooseX::Getopt with usage message and man page generated from attribute meta and POD. River stage two • 9 direct dependents • 13 total dependents

Perl Moose Role that extends MooseX::Getopt to provide usage printing and man page generation that inspects your classes meta information to build a (coloured) usage message including that meta information. If STDOUT is a tty usage message is colouri...

PITCHLESS/MooseX-Getopt-Usage-0.24 - 25 Sep 2014 16:09:35 UTC

MooseX::Daemonize::Pid::File - PID file management for MooseX::Daemonize River stage two • 9 direct dependents • 16 total dependents

This object extends MooseX::Daemonize::Pid to add persistence in a Pidfile. This class sets up some basic coercion routines for itself so that it can be created from a *Str* (a file name), *ArrayRef* (an array of path components for a filename) or a ...

ETHER/MooseX-Daemonize-0.22 - 07 Dec 2019 01:26:55 UTC

MooseX::Daemonize::WithPidFile - A Role with the core daemonization and pidfile management River stage two • 9 direct dependents • 16 total dependents

This is a slightly extended basic daemonization Role, it provides Pidfile management along with the core daemonization features found in MooseX::Daemonize::Core....

ETHER/MooseX-Daemonize-0.22 - 07 Dec 2019 01:26:55 UTC

MooseX::Role::Cmd::Meta::Attribute::Trait - Optional meta attribute trait for custom option names River stage one • 1 direct dependent • 1 total dependent

Provides some extra markup to help MooseX::Role::Cmd decide how to use command line parameters....

EDENC/MooseX-Role-Cmd-0.10 - 07 Dec 2010 05:37:27 UTC

MooseX::Runnable::Invocation::Scheme::MooseX::Getopt - run MX::Getopt classes River stage one • 2 direct dependents • 2 total dependents

This role will be used by "MooseX::Runnable::Invocation" to create an instance of the class to be run with "MooseX::Getopt". Any args not consumed by MX::Getopt will be passed to the class's run method. (See the test "t/basic-mx-getopt.t" for an exam...

ETHER/MooseX-Runnable-0.10 - 13 Mar 2016 00:42:15 UTC
8 results (0.065 seconds)