Ports Search

This module adds XPath-style matching to your object trees. This means that you can find nodes using an XPath-esque query with "match()" from anywhere in the tree. Also, the "xpath()" method returns a unique path to a given node which can be used as an identifier. NOTE: This module is not yet a complete XPath implementation. Over time I expect the subset of XPath supported to grow. See the SYNTAX documentation in the module POD for details on the current level of support.

This module allows to perform schema based configuration validation. The idea is to define in a schema what valid data is. This schema can be used to create a validator object that can in turn be used to make sure that some data indeed conforms to the schema. Although the primary focus is on "configuration" (for instance as provided by modules like Config::General) and, to a lesser extent, "options" (for instance as provided by modules like Getopt::Long), this module can in fact validate any data structure.

DateTime::Calendar::Hebrew is the implementation of the Hebrew calendar. Read on for more details on the Hebrew calendar. The Hebrew/Jewish calendar is a Luni-Solar calendar. Torah Law mandates that months are Lunar. The first day of a month coincides with the new moon in Jerusalem. (In ancient times, this was determined by witnesses. Read the books in the bibliography for more info). The Torah also mandates that certain holidays must occur in certain seasons. Seasons are solar, so a calendar that can work with lunar & solar events is needed.

DateTime::Format::Builder creates DateTime parsers. Many string formats of dates and times are simple and just require a basic regular expression to extract the relevant information. Builder provides a simple way to do this without writing reams of structural code. Builder provides a number of methods, most of which you'll never need, or at least rarely need. They're provided more for exposing of the module's innards to any subclasses, or for when you need to do something slightly beyond what I expected.

ExtUtils::InstallPaths tries to make install path resolution as easy as possible. When you want to install a module, it needs to figure out where to install things. The nutshell version of how this works is that default installation locations are determined from ExtUtils::Config, and they may be individually overridden by using the install_path attribute. An install_base attribute lets you specify an alternative installation root like /home/foo and prefix does something similar in a rather different (and more complicated) way. destdir lets you specify a temporary installation directory like /tmp/install in case you want to create bundled-up installable packages.

rth is a web-based tool designed to manage requirements, tests, test results, and defects throughout the application life cycle. The tool provides a structured approach to software testing and increases the visibility of the testing process by creating a common repository for all test assets including requirements, test cases, test plans, and test results. Regardless of their geographic location, rth allows testers, developers, business analysts, and managers to monitor and gauge application readiness. The tool includes modules for requirements management, test planning, test execution, defect tracking, and reporting.

IO-stringy makes it possible to create perl filehandles that point to just about any object. It contains next modules: IO::AtomicFile - write a file which is updated atomically IO::InnerFile - define a file inside another file IO::Lines - IO:: interface for reading/writing an array of lines IO::Scalar - IO:: interface for reading/writing a scalar IO::ScalarArray - IO:: interface for reading/writing an array of scalars IO::Wrap - wrap raw filehandles in IO::Handle interface IO::WrapTie - wrap tieable objects in IO::Handle interface

IPC::MMA provides an interface to Ralf Engelschall's mm library, allowing memory to be shared between multiple processes in a relatively convenient way. IPC::MMA is a superset of Arthur Choung's IPC::MM module, adding arrays and allowing any Perl scalar to be used as a hash/BTree key rather than just C strings. IPC::MMA hashes are like IPC::MM BTrees in that they return keys in sorted order ineach, keys, and next operations. An IPC::MMA array can store data in any of six ways, including general-purpose scalars, signed or unsigned integers, floating-point numbers, fixed-length strings/records, and booleans at one bit per array element.

Log::Dump is a simple logger mix-in mainly for debugging. This installs six methods into a caller (the class that used Log::Dump) via Sub::Install. The point is you don't need to load extra dumper modules or you don't need to concatenate messages. Just log things and they will be dumped (and concatenated if necessary) to stderr, and to a file if you prefer. Also, you can use these logging methods as class methods or object methods (though usually you don't want to mix them, especially when you're doing something special).

Module::Extract is a convenience base class for creating module that work with Perl distributions. Its purpose is to take care of the mechanisms of locating and extracting a Perl distribution so that your module can do something specific to the distribution. This module was originally created to provide an abstraction for the extraction logic for both Module::Inspector and Module::P4P and to allow additional features to be added in the future without having to modify both of them, because the general problem of "locate, download, and expand a distribution" is one that is almost ideal for adding additional features down the line.