This module fills a gap in Moose by adding method parameter
validation to Moose. This is just one of many developing options,
it should not be considered the "official" one by any means though.
Net::DBus provides a Perl XS API to the dbus inter-application
messaging system. The Perl API covers the core base level
of the dbus APIs, not concerning itself yet with the GLib
or QT wrappers
MooseX::Role::WithOverloading allows you to write a Moose::Role which
defines overloaded operators and allows those operator overloadings
to be composed into the classes/roles/instances it's compiled to,
while plain Moose::Roles would lose the overloading.
Simply loading the MooseX::StrictConstructor module makes your
constructors "strict". If your constructor is called with an attribute
init argument that your class does not declare, then it calls
"Carp::confess()". This is a great way to catch small typos.
MooseX::Types::VariantTable implements a simple dispatch table based on
Moose type constraints.
Subtypes will be checked before their parents, meaning that the order of
the declaration does not matter.
From the website:-
This library allows to interface with a smart card and pcsc-lite using the
Perl language. The archive contains the Perl wrapper and sample code.
Bruce
bms@spc.org
This Perl module parses ctags files and handles both traditional
ctags as well as extended ctags files such as produced with Exuberant
ctags.
The module is implemented as a wrapper around the readtags library
that normally ships with Exuberant ctags.
This perl module will eval another perl script and return a hash ref
of the final values of the global variables in the eval. This allows
you to write generic config files in Perl.
If you need nonblocking access to an external program, or want to execute some
blocking code in a separate process, but you don't want to write a wrapper
module or some POE::Wheel::Run boilerplate code, then POE::Quickie can help.
You just specify what you're interested in (stdout, stderr, and/or exit code),
and POE::Quickie will handle the rest in a sensible way.
It has some convenience features, such as killing processes after a timeout,
and storing process-specific context information which will be delivered with
every event.
There is also an even lazier API which suspends the execution of your event
handler and gives control back to POE while your task is running, the same
way LWP::UserAgent::POE does.
This is provided by the quickie_* functions which are exported by default.
POE::Stage is a proposed base class for POE components. Its purpose is
to standardize the most common design patterns that have arisen through
years of POE::Component development.