This module provides a more general version of the Str type. If
coercions are enabled, it will accepts objects that overload
stringification and coerces them into strings.
This module exports one function, declare, for building named objects
with a declarative syntax, similar to how Jifty::DBI::Schema defines
its columns.
This module provides a 'parallel map'. Multiple worker processes are
forked so that many instances of the transformation function may be
executed simultaneously.
POE::Component::RSS is an event based RSS parsing module. It wraps
XML::RSS and provides a POE based framework for accessing the information
provided.
POW::Component::RSSAggregator is a non-blocking way to watch
multiple RSS sources with one process.
See also p5-XML-RSS-Feed.
This class is an implementation of the abstract POE::Queue interface.
It implements a priority queue using C, with an XS interface supplied.
Path::Resource is a module for combining local file and directory manipulation
with URI manipulation. It allows you to effortlessly map local file locations
to their URI equivalent.
PerlIO::utf8_strict provides a fast and correct UTF-8 PerlIO layer. Unlike
perl's default :utf8 layer it checks the input for correctness.
This module exports a number of wrappers around perl's builtin grok_number
function, which returns the numeric type of its argument, or 0 if it isn't
numeric.
Aegis is a transaction-based software configuration management system. It
provides a framework within which a team of developers may work on many
changes to a program independently, and Aegis coordinates integrating these
changes back into the master source of the program, with as little disruption
as possible. Some key features:
* All operations on the repository are based on change sets.
* True configurations. All changes are reproducible snapshots. Every change
set has a unique configuration identifier.
* Ability to rename files without losing their history.
* Binary files are supported.
* File meta-data are versioned. Aegis versions permissions also.
* Commits are truly atomic. No part of a commit takes effect until the entire
commit has succeeded. Log messages are attached to the change set, not
stored redundantly in each file.
* Access controls on lines of development (branches). Creating a branch in
Aegis can be accomplished with a single, fast command.
* Repository synchronization, geographically distributed development.
* Optimal performance for all users, local or remote (no difference).
* Disconnected commits.
* Peer-to-peer architecture. Work may flow in without involving a master site.
* Costs are proportional to change size, not data size.