A Hash::AsObject is a blessed hash that provides read-write access to its
elements using accessors. (Actually, they're both accessors and mutators.)
It's designed to act as much like a plain hash as possible; this means,
for example, that you can use methods like DESTROY and if the Hash::AsObject
has an element with that name, it'll get or set it.
Many Perl distributions use a Build.PL file instead of a Makefile.PL file to
drive distribution configuration, build, test and installation. Traditionally,
Build.PL uses Module::Build as the underlying build system. This module provides
a simple, lightweight, drop-in replacement.
Whereas Module::Build has over 6,700 lines of code; this module has less than
70, yet supports the features needed by most pure-Perl distributions.
Nuxi CloudABI is an application binary interface for UNIX-like operating
systems built around the concept of capability-based security. In a
nutshell, it means that you can run processes directly on top of a UNIX
kernel while keeping complete control over the actions the process is
allowed to perform.
This port installs a set of header files that contain the definitions
that describe the ABI itself: all of the constants, types, structures
and system calls.
MooseX::Types::Signal exports a type, Signal, that recognizes valid signals
on your platform. The underlying type is a non-negative number, but there is
a coercion from strings to numbers that recognizes signals by name.
There are also more restrictive types, PerlSignal and UnixSignal. UnixSignal
only understands signals that are in your system's signal.h header file.
PerlSignal only understands signals that are in Perl's %Config hash. Signal
is either/or, with preference to UnixSignal over PerlSignal when coercing.
POEx::Role::SessionInstantiation provides a nearly seamless
integration for non-POE objects into a POE environment. It does this
by handling the POE stuff behind the scenes including allowing per
instances method changes, session registration to the Kernel, and
providing some defaults like setting an alias if supplied via the
attribute or constructor argument, or defining a _default that warns
if your object receives an event that it does not have.
This role exposes your class' methods as POE events.
The Params::Validate module allows you to validate method or function
call parameters to an arbitrary level of specificity. At the simplest
level, it is capable of validating the required parameters were given
and that no unspecified additional parameters were passed in. It is
also capable of determining that a parameter is of a specific type,
that it is an object of a certain class hierarchy, that it possesses
certain methods, or applying validation callbacks to arguments.
Pragmatic implements a default import method for processing pragmata before
passing the rest of the import to Exporter.
Perl automatically calls the import method when processing a use statement for a
module. Modules and use are documented in perlfunc and perlmod.
(Do not confuse Pragmatic with pragmatic modules, such as less, strict and the
like. They are standalone pragmata, and are not associated with any other
module.)
This module iterates over files and directories to identify ones
matching a user-defined set of rules. The API is based heavily on
File::Find::Rule, but with more explicit distinction between matching
rules and options that influence how directories are searched. A
Path::Iterator::Rule object is a collection of rules (match criteria)
with methods to add additional criteria. Options that control
directory traversal are given as arguments to the method that
generates an iterator.
This module does a compile-time code injection to let you define subroutine
aliases based on its name.
This differs from p5-Sub-Name in that it defines a typeglob in a more correct
way and keeps you from manipulating the symbols table directly. You can use
the subroutine as if it was defined the ordinary way then.
This is particularly useful in the cases when you need to have several
identical subroutines with different names.
The POSIX standard provides three functions for converting between integer
epoch values and 6-component "broken-down" time representations.
localtime and gmtime convert an epoch into the 6 components of seconds,
minutes, hours, day of month, month and year, in either local timezone or UTC.
The mktime function converts a local broken-down time into an epoch value.
However, POSIX does not provide a UTC version of this.
This module provides a function timegm which has this ability.