Results 3,371–3,380 of 5,623 for /devel/.(0.003 seconds)
Restores ties to an existing object
Provides the opposite of the 'tied' function. Say you have %hash that
is tied to $object. Then, it is relatively simple to get $object from
%hash simply by saying
$object = tied %hash;
But, how does one go the other way? Simple, with Tie::Restore
tie %hash, 'Tie::Restore', $object;
Works for any kind of tie. (scalar, array, hash, filehandle)
Utilities to test STDOUT and STDERR messages
Test::Output provides a simple interface for testing output sent to
STDOUT or STDERR. A number of different utilities are included to try
and be as flexible as possible to the tester.
Originally this module was designed not to have external requirements,
however, the features provided by Sub::Exporter over what Exporter
provides is just to great to pass up.
Test::Output ties STDOUT and STDERR using Test::Output::Tie.
POE Component providing TCP client services for test cases
Test::POE::Client::TCP is a POE component that provides a TCP client
framework for inclusion in client component test cases, instead of
having to roll your own.
Utility functions for fiddling with tied variables
This module provides a few subroutines for examining and modifying tied
variables, including those that hold weak references to the objects to
which they are tied (weak ties).
Tie iCal files to Perl hashes
Tie::iCal represents an RFC2445 iCalendar file as a Perl hash. Each key in the
hash represents an iCalendar component like VEVENT, VTODO or VJOURNAL. Each
component in the file must have a unique UID property as specified in the RFC
2445. A file containing non-unique UIDs can be converted to have only unique
UIDs (see samples/uniquify.pl).
The module makes very little effort in understanding what each iCalendar
property means and concentrates on the format of the iCalendar file only.
POE Component providing TCP server services for test cases
Test::POE::Server::TCP is a POE component that provides a TCP server
framework for inclusion in client component test cases, instead of
having to roll your own.
Parsing log files from test runs, and displays in an XML syntax
This module serves as a common base class for test log parsers. These
tools are intended to be able to parse output from a wide variety of
tests - including non-Perl tests.
The parsers also write the test data into the 'Test Result Publication
Interface' (TRPI) XML schema, developed by SpikeSource. See
http://www.spikesource.com/testresults/index.jsp?show=trpi-schema
Perl extension to check that all your files are tidy
Test::PerlTidy - check that all your files are tidy.
Checks for pod coverage regression
Checks for pod coverage regression.
Easy-to-use date/time formatting
Time::Format provides a very easy way to format dates and times. The
formatting functions are tied to hash variables, so they can be used
inside strings as well as in ordinary expressions. The formatting
codes used are meant to be easy to remember, use, and read. They
follow a simple, consistent pattern. If I've done my job right, once
you learn the codes, you should never have to refer to the
documentation again.
A quick-reference page is included, just in case. ;-)
Time::Format can also format DateTime objects, and strings created
with Date::Manip.
Also provided is a tied-hash interface to POSIX::strftime and
Date::Manip::UnixDate.
If the I18N::Langinfo module is available, Time::Format provides
weekday and month names in a language appropriate for your locale.
A companion module, Time::Format_XS, is also available; if it is
installed, Time::Format will detect and use it, which will result in a
significant speed improvement.