mirror of
https://git.freebsd.org/ports.git
synced 2025-07-18 17:59:20 -04:00
Hunt for typos in devel/p5-*.
This commit is contained in:
Jimmy Olgeni
parent
6d4aa839c8
commit
f532e2405a
Notes:
svn2git
2021-03-31 03:12:20 +00:00
svn path=/head/; revision=213563
127 changed files with 155 additions and 155 deletions
|
|
@ -4,7 +4,7 @@ fields, and each field is a scalar or a list(arrayref).
|
|||
|
||||
The basic usage is you walk through all your logs, and use append_data()
|
||||
to insert each rows, (you'll have to split the line into fields), and
|
||||
then call result() to retrieve the result, or report() to immediatly
|
||||
then call result() to retrieve the result, or report() to immediately
|
||||
see simple result.
|
||||
|
||||
You may specify a filed_groups parameter (arrayref of arrayref), and
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Algorithm::Annotate generates a list that is useful for generating
|
||||
output simliar to "cvs annotate".
|
||||
output similar to "cvs annotate".
|
||||
|
||||
WWW: http://search.cpan.org/dist/Algorithm-Annotate/
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ into it's own module because I found myself copying and pasting
|
|||
it way too often for various needs. Most of the uses I have for
|
||||
C3 revolve around class building and metamodels, but it could
|
||||
also be used for things like dependency resolution as well since
|
||||
it tends to do such a nice job of preserving local precendence
|
||||
it tends to do such a nice job of preserving local precedence
|
||||
orderings.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Algorithm-C3/
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
Algorithm::Dependency is a framework for creating simple read-only
|
||||
dependency heirachies, where you have a set of items that rely on other
|
||||
dependency hierarchies, where you have a set of items that rely on other
|
||||
items in the set, and require actions on them as well.
|
||||
|
||||
Despite the most visible of these being software installation systems like
|
||||
the CPAN installer, or debian apt-get, they are usefull in other
|
||||
the CPAN installer, or debian apt-get, they are useful in other
|
||||
situations. This module intentionally uses implementation-neutral words,
|
||||
to avoid confusion.
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ It's a library for doing evolutionary computation in Perl.
|
|||
Algorithm::Evolutionary was formerly called OPEAL, which is an acronym for
|
||||
Obvious Pearl Evolutionary Algorithm Library.
|
||||
|
||||
The desing principles of Algorithm::Evolutionary are:
|
||||
The design principles of Algorithm::Evolutionary are:
|
||||
* It should be easy to program any kind of evolutionary algorithm; all
|
||||
chromosome representations and operators are possible.
|
||||
* An XML dialect called EvoSpec is used as a language for description of
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Algorithm::MarkovChain implements a class capable of creating a Markov
|
||||
chain, and then generating output based on it. For more information
|
||||
consult the Algorithm::MarkovChain(3) manpage.
|
||||
consult the Algorithm::MarkovChain(3) man page.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Algorithm-MarkovChain/
|
||||
Author: Richard Clamp <richardc@unixbeard.net>
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Algorithm::SVM implements a Support Vector Machine for Perl.
|
||||
Support Vector Machines provide a method for creating classifcation
|
||||
Support Vector Machines provide a method for creating classification
|
||||
functions from a set of labeled training data, from which predictions
|
||||
can be made for subsequent data sets.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ Alias is a perl module that performs aliasing services. It is useful for
|
|||
those of you that are tired of dereferencing hash-based object attributes,
|
||||
or wish perl could make-do with fewer $, -> and {} things, or are a little
|
||||
scared of using typeglobs, or want the freedom to put what you want, when you
|
||||
want in the symbol table without having to deal with wierd syntax, or need
|
||||
want in the symbol table without having to deal with weird syntax, or need
|
||||
to use scalar constants in your program since you don't trust yourself from
|
||||
changing $PI (heh). Most notably, there is a C<attr> function that installs
|
||||
a whole hash on the symbol table with implicit localization. This allows
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This package contains a data modelling GUI for Alzabo implemented with
|
||||
This package contains a data modeling GUI for Alzabo implemented with
|
||||
HTML::Mason.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Alzabo-GUI-Mason/
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Alzabo is a suite of modules with two core functions. Its first use is as a
|
||||
data modelling tool. Through either a schema creation GUI, a perl program, or
|
||||
data modeling tool. Through either a schema creation GUI, a perl program, or
|
||||
reverse engineering, you can create a set objects to represent a schema.
|
||||
|
||||
Its second function is as an RDBMS to object mapping system. Once you have
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
The rather wacky idea behind this module and its sister module DBD::AnyData
|
||||
is that any data, regardless of source or format should be accessable and
|
||||
is that any data, regardless of source or format should be accessible and
|
||||
modifiable with the same simple set of methods. This module provides a multi-
|
||||
dimensional tied hash interface to data in a dozen different formats. The
|
||||
DBD::AnyData module adds a DBI/SQL interface for those same formats.
|
||||
|
|
@ -8,7 +8,7 @@ Both modules provide built-in protections including appropriate flocking()
|
|||
for all I/O and (in most cases) record-at-a-time access to files rather than
|
||||
slurping of entire files.
|
||||
|
||||
Currently supported formats include general format flatfiles (CSV, Fixed
|
||||
Currently supported formats include general format flat files (CSV, Fixed
|
||||
Length, etc.), specific formats (passwd files, httpd logs, etc.), and a
|
||||
variety of other kinds of formats (XML, Mp3, HTML tables). The number of
|
||||
supported formats will continue to grow rapidly since there is an open API
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ and data structures, providing much faster use when the data is cached.
|
|||
This module stores data in the home directory of the user, in a dot
|
||||
directory. For example, the Parse::BACKPAN::Packages cache is actually
|
||||
stored underneath "~/.parse_backpan_packages/cache/". This is so that
|
||||
permisssions are not a problem - it is a per-user, per-application cache.
|
||||
permissions are not a problem - it is a per-user, per-application cache.
|
||||
|
||||
WWW: http://search.cpan.org/dist/App-Cache/
|
||||
Author: Leon Brocard <acme@astray.com>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
This module was mainly written for Net::XMPP2, Net::IRC3 and BS to
|
||||
provide a consistent API for registering and emitting events. Even
|
||||
though I originally wrote it for those modules I relased it seperately
|
||||
though I originally wrote it for those modules I released it separately
|
||||
in case anyone may find this module useful.
|
||||
|
||||
WWW: http://search.cpan.org/dist/BS-Event/
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This module's default exports override the core stat() and lstat()
|
||||
functions, replacing them with versions that contain BSD 4.4 extentions
|
||||
functions, replacing them with versions that contain BSD 4.4 extensions
|
||||
such as flags. This module also adds chflags function.
|
||||
|
||||
WWW: http://search.cpan.org/dist/BSD-stat/
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
The "CPANPLUS" library is an API to the "CPAN" mirrors and a
|
||||
collection of interactive shells, commandline programs, daemons, etc,
|
||||
collection of interactive shells, command line programs, daemons, etc,
|
||||
that use this API.
|
||||
|
||||
WWW: http://cpanplus.sourceforge.net/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Class::Accessor is a great way to automate the tedious task of
|
||||
generating accessors and mutators. One small drawback is that due to
|
||||
the details of the implemenetation, you only get one __ANON__ entry in
|
||||
the details of the implementation, you only get one __ANON__ entry in
|
||||
profiling output. That entry contains all your accessors, which can be
|
||||
a real pain if you're attempting to figure out which of your accessors
|
||||
is being called six billion times. This module is a development aid
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Class::AutoClass => similar to Class::MakeMethods, provides support for:
|
||||
- automatically generating mutator methods for simple values,
|
||||
- allows for automatic attribute initialization and default value
|
||||
initilaization,
|
||||
initialization,
|
||||
- object initialization is handled correctly (in top-down order), even
|
||||
in the presence of multiple inheritance
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Class::CodeStyler is an object oriented API to be used by code-gererators
|
||||
Class::CodeStyler is an object oriented API to be used by code-generators
|
||||
in producing formatted code (Perl, C, other). The produced code file can
|
||||
also be syntax checked, displayed with line numbers, executed, and eval'd.
|
||||
Code can be inserted anywhere in the generated program using a system of
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Class::Data::Inheritable is for creating accessor/mutators to class
|
||||
data. That is, if you want to store something about your class as a
|
||||
whole (instead of about a single object). This data is then inherited
|
||||
by your subclasses and can be overriden.
|
||||
by your subclasses and can be overridden.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Class-Data-Inheritable/
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
Class::Default provides a mechanism to allow your class to take static
|
||||
method calls and apply it to a default instantiation of an object. It
|
||||
provides a flexibility to an API that allows it to be used more
|
||||
confortably in different situations.
|
||||
comfortably in different situations.
|
||||
|
||||
This technique appears to be especially usefull when writing modules
|
||||
that you want to be used in either a single use or a persistant
|
||||
This technique appears to be especially useful when writing modules
|
||||
that you want to be used in either a single use or a persistent
|
||||
environment. In a CGI like environment, you want the simplicity of a
|
||||
static interface. You can call Class-method> directly, without having
|
||||
to pass an instantiation around constantly.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Set of modules:
|
||||
|
||||
* Class::Fields - inspect the fields of a class
|
||||
* Class::Fields::Fuxor - low level manipuation of object data members
|
||||
* Class::Fields::Fuxor - low level manipulation of object data members
|
||||
* private - add private data members to Perl classes
|
||||
* protected - "private" data fields which are inherited by child classes
|
||||
* public - add public data members to Perl classes
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ members, required members, private members, methods (both
|
|||
instance and class), and other common features of object-
|
||||
oriented software development. Of course, you can implement all
|
||||
these things without a special module, but doing it via
|
||||
Class::Generate is much, much more concise. And futhermore,
|
||||
Class::Generate is much, much more concise. And furthermore,
|
||||
it's much less error prone: if you are using Perl's -w flag,
|
||||
Class::Generate will catch many class specification and usage
|
||||
errors.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ different modules. Class::Handle attempts to provide a convenient
|
|||
object wrapper around the various different types of functions that can
|
||||
be performed on a class.
|
||||
|
||||
Currently, Class::Handle provies what is effectively a combined API from
|
||||
Currently, Class::Handle provides what is effectively a combined API from
|
||||
UNIVERSAL, Class::ISA and Class::Inspector for obtaining information
|
||||
about a Class, and some additional task methods, such as load to common
|
||||
tasks relating to classes.
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
Class::Hook enables you to trace methods calls from your code to other classes.
|
||||
|
||||
Instead of putting 'use Foo;' in your code, simply type 'use Class::Hook;'.
|
||||
The class Foo is unknown in your code. It will be magically catched by
|
||||
The class Foo is unknown in your code. It will be magically caught by
|
||||
Class::Hook which will call Foo itself. You can see Class::Hook as a kind of
|
||||
relay.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Yet another implementation of an anonymous class with per object
|
||||
overrideable methods, but with the added attraction of sort of working
|
||||
overridable methods, but with the added attraction of sort of working
|
||||
dispatch to the parent class's method.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Class-Inner/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Class::Inspector allows you to get information about a loaded class.
|
||||
Most or all of this information can be found in other ways, but they
|
||||
arn't always very friendly, and usually involve a relatively high level
|
||||
aren't always very friendly, and usually involve a relatively high level
|
||||
of Perl wizardry, or strange or unusual looking code. Class::Inspector
|
||||
attempts to provide an easier, more friendly interface to this
|
||||
information.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
from the readme:
|
||||
from the README:
|
||||
|
||||
This module solves the problem of having to write a bazillion get/set
|
||||
methods that are all the same. The argument to 'use' is a hash whose keys
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
This module is an alternative to Class::Singleton and
|
||||
Class::WeakSingleton, and provides a more secure Singleton class in that
|
||||
it takes steps to prevent the possibility of accidental creation of
|
||||
multiple instances and/or the overwriting of existsing Singleton
|
||||
multiple instances and/or the overwriting of existing Singleton
|
||||
instances.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Class-StrongSingleton/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
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 unqique path
|
||||
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
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ well as removing all the Pure Perl from the More.pm, I was able to
|
|||
gain a lot of speed out of the module. Essentially, though, the core
|
||||
of the module is exactly as that of Clone::More.
|
||||
|
||||
You will see that by useing Benchmark::cmpthese, I ran a simple
|
||||
You will see that by using Benchmark::cmpthese, I ran a simple
|
||||
comparison between Storable::dclone, Clone::More::clone, and
|
||||
Clone::Fast::clone. You will (should) begin to see the reason why I
|
||||
loaded this module along side of Clone::More.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
This is intended to act as a utility in order to natively clone data
|
||||
structures via a simple Perl interface. Will ensure that all
|
||||
references will be separated from the parent data strure, yet kept
|
||||
references will be separated from the parent data structure, yet kept
|
||||
relative to the new structure (if need be).
|
||||
|
||||
WWW: http://search.cpan.org/dist/Clone-More/
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ Code::Perl allows you to build chunks of Perl code as a tree and then when
|
|||
you're finished building, the tree can output the Perl code. This is
|
||||
useful if you have built your own mini-language and you want to generate
|
||||
Perl from it. Rather than generating the Perl at parse time and having to
|
||||
worry about quoting, escaping, parenthese etc, you can just build a tree
|
||||
worry about quoting, escaping, parentheses etc, you can just build a tree
|
||||
using Code::Perl and then dump out the correct Perl at the end.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Code-Perl
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Config::General handles configuration files of a format inspired by
|
||||
Apache's httpd.conf file format. It features some enhancements such
|
||||
as here-documents, C-style commends and multiline options. Both
|
||||
as here-documents, C-style commends and multi-line options. Both
|
||||
reading and writing of configuration files is supported.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Config-General/
|
||||
|
|
|
|||
|
|
@ -14,9 +14,9 @@ Get a new Config::IniFiles object with the *new* method:
|
|||
Optional named parameters may be specified after the configuration file
|
||||
name. See the *new* in the METHODS section, below.
|
||||
|
||||
INI files consist of a number of sections, each preceeded with the
|
||||
INI files consist of a number of sections, each preceded with the
|
||||
section name in square brackets. Parameters are specified in each section
|
||||
as Name=Value. Any spaces around the equals sign will be i gnored, and the
|
||||
as Name=Value. Any spaces around the equals sign will be ignored, and the
|
||||
value extends to the end of the line.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Config-IniFiles/
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ on a per-host basis, or even using an environment variable.
|
|||
By default a win.ini style of configuration is used, but this can
|
||||
be overridden and an XML based configuration is also included. The
|
||||
access mechanism can also be overridden, the setting don't have to
|
||||
come from a file, but (maybe) from a website. You'll have to write
|
||||
come from a file, but (maybe) from a web site. You'll have to write
|
||||
your own there, though.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Config-Setting/
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
Contextual::Return - Create context-senstive return values.
|
||||
Contextual::Return - Create context-sensitive return values.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Contextual-Return/
|
||||
|
|
|
|||
|
|
@ -2,8 +2,8 @@ This module collection manages coroutines. Coroutines are similar to
|
|||
threads but don't run in parallel.
|
||||
|
||||
In this module, coroutines are defined as "callchain + lexical variables
|
||||
+ @_ + $_ + $@ + $^W + C stack), that is, a coroutine has it's own
|
||||
callchain, it's own set of lexicals and it's own set of perl's most
|
||||
+ @_ + $_ + $@ + $^W + C stack), that is, a coroutine has its own
|
||||
callchain, its own set of lexicals and its own set of perl's most
|
||||
important global variables.
|
||||
|
||||
Author: Marc Lehmann <pcg@goof.com>
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Data::Alias is a module that allows you to apply "aliasing semantics"
|
||||
to a section of code, causing aliases to be made whereever Perl would
|
||||
to a section of code, causing aliases to be made wherever Perl would
|
||||
normally make copies instead. You can use this to improve efficiency
|
||||
and readability, when compared to using references.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Data::Hexdumper provides a simple way to format and display arbitary binary
|
||||
Data::Hexdumper provides a simple way to format and display arbitrary binary
|
||||
data in a way similar to how some debuggers do for lesser languages. It
|
||||
gives the programmer a considerable degree of flexibility in how the data is
|
||||
formatted, with sensible defaults. It is envisaged that it will primarily be
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
A very little module for simulating lazines in perl. It provides
|
||||
A very little module for simulating laziness in perl. It provides
|
||||
scalars that are "lazy", that is their value is computed only if
|
||||
necessary and at most once.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This module provides a round roubin object implementation. It is similar
|
||||
to an iterator, only the internal counter is reset to the begining
|
||||
This module provides a round robin object implementation. It is similar
|
||||
to an iterator, only the internal counter is reset to the beginning
|
||||
whenever it reaches the end. It might also be considered as a circular
|
||||
iterator.
|
||||
|
||||
|
|
|
|||
|
|
@ -11,5 +11,5 @@ input (except for HTML). Individual or ranges of columns may be selected
|
|||
for display, either by name or by index.
|
||||
|
||||
In other words, showtable is a data formatting program. Using the '-html'
|
||||
option, showtable can accept ASCII tablular data and format it appropriately
|
||||
option, showtable can accept ASCII tabular data and format it appropriately
|
||||
for display through a Web-browser.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This module is for manipulating data as hierarchical tag/value pairs
|
||||
(Structured TAGs or Simple Tree AGgreggates). These datastructures can
|
||||
(Structured TAGs or Simple Tree AGgreggates). These data structures can
|
||||
be represented as nested arrays, which have the advantage of being
|
||||
native to perl.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@
|
|||
Among other things, Date::Manip allow you to:
|
||||
|
||||
1. Enter a date and be able to choose any format
|
||||
conveniant
|
||||
convenient
|
||||
|
||||
2. Compare two dates, entered in widely different formats
|
||||
to determine which is earlier
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Date::Set is a module for date/time sets. It allows you to generate
|
||||
groups of dates, like "every wednesday", and then find all the dates
|
||||
groups of dates, like "every Wednesday", and then find all the dates
|
||||
matching that pattern.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Date-Set/
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
DateTime::Calendar::FrenchRevolutionary implements the French Revolutionary
|
||||
Calendar. This module implements most methods of DateTime; see the DateTime(3)
|
||||
manpage for all methods.
|
||||
man page for all methods.
|
||||
|
||||
WWW: http://datetime.perl.org/
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
DateTime::Calendar::Julian implements the Julian Calendar. This module
|
||||
implements all methods of DateTime; see the DateTime(3) manpage for all
|
||||
implements all methods of DateTime; see the DateTime(3) man page for all
|
||||
methods.
|
||||
|
||||
WWW: http://datetime.perl.org/
|
||||
|
|
|
|||
|
|
@ -1,9 +1,9 @@
|
|||
This module allows you to calulate the day, week, period or quarter of a date
|
||||
This module allows you to calculate the day, week, period or quarter of a date
|
||||
in a fiscal year, given a start date and either a target date or number of
|
||||
periods and target date. This is often needed in business, where the fiscal
|
||||
year begins and ends on different days than the calendar year. This module is
|
||||
based on the Gregorian calendar. Using other DT calendar objects will return
|
||||
results, but the behavior is unpredicatable for calendars that have more than
|
||||
results, but the behavior is unpredictable for calendars that have more than
|
||||
365 or 366 days.
|
||||
|
||||
WWW: http://datetime.perl.org/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Declaring constants is very convenient for writing programs, but as
|
||||
they're often inlined by Perl, retrieving their symbolic names can be
|
||||
tricky. This is made worse with lowlevel modules that use constants for
|
||||
tricky. This is made worse with low level modules that use constants for
|
||||
bit-twiddling.
|
||||
|
||||
Devel::Constants makes this much more manageable.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This module provides tracking of objects, for the purpose of detecting
|
||||
memory leaks due to circular references or innappropriate caching
|
||||
memory leaks due to circular references or inappropriate caching
|
||||
schemes.
|
||||
|
||||
Object tracking can be enabled on a per object basis or globally. Any
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Description from the homepage:
|
||||
Description from the home page:
|
||||
|
||||
Devel::LexAlias provides the ability to alias a lexical variable in a
|
||||
subroutines scope to one of your choosing.
|
||||
|
|
|
|||
|
|
@ -2,9 +2,9 @@ The Devel::Modlist perl module provides a means by which to get a
|
|||
quick run-down on which libraries and modules are being utilized
|
||||
by a given perl script.
|
||||
|
||||
Just as compiler systems like gcc provide dependancy information
|
||||
Just as compiler systems like gcc provide dependency information
|
||||
via switches such as -M, Devel::Modlist is intended to assist script
|
||||
authors in preparing dependancy information for potential users of
|
||||
authors in preparing dependency information for potential users of
|
||||
their scripts.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Devel-Modlist/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Perl has changed over time, gaining new features, new functions, increasing its
|
||||
flexibility, and reducing the impact on the C namespace environment (reduced
|
||||
pollution). The header file, typicaly ppport.h, written by this module attempts
|
||||
pollution). The header file, typically ppport.h, written by this module attempts
|
||||
to bring some of the newer Perl features to older versions of Perl, so that you
|
||||
can worry less about keeping track of old releases, but users can still reap
|
||||
the benefit.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ environment of an author of a CPAN module (or more precisely: a user of the
|
|||
ExtUtils::MakeMaker module). It makes sure that any changes to the required
|
||||
modules specified in the Makefile.PL are automatically reflected in the
|
||||
appropriate text file and in the appropriate source files (either
|
||||
explicitely or implicitely specified).
|
||||
explicitly or implicitly specified).
|
||||
|
||||
It takes the information given with the PREREQ_PM parameter and by default
|
||||
writes this to the README file, as well as to the POD of the file specified
|
||||
|
|
|
|||
|
|
@ -1,11 +1,11 @@
|
|||
Provides shared memory structures (using memory mapped files via
|
||||
IPC::Mmap) to be used by diagnostic and debugger applications for Perl
|
||||
scripts (see Devel::STrace). Using XS/C code to maximize performance,
|
||||
creates a set of ringbuffers with a configurable number of slots. Each
|
||||
slot includes a field for a linenumber, a timestamp, and a fully
|
||||
creates a set of ring buffers with a configurable number of slots. Each
|
||||
slot includes a field for a line number, a timestamp, and a fully
|
||||
qualified subroutine name. Each ring buffer also includes additional
|
||||
headers and fields to support diagnostic interfaces, e.g., watched
|
||||
expressions, command/reponse interfaces to the monitored applications,
|
||||
expressions, command/response interfaces to the monitored applications,
|
||||
etc.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Devel-RingBuffer/
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ Features include:
|
|||
To debug a script using ptkdb invoke perl like this:
|
||||
perl -d:ptkdb myscript.pl
|
||||
|
||||
ptkdb can easily be used to debug CGI scripts if your webserver box is
|
||||
ptkdb can easily be used to debug CGI scripts if your web server box is
|
||||
capable of running Perl/Tk applications. Just change the shebang line of your
|
||||
scripts to:
|
||||
#! /usr/bin/perl -w -d:ptkdb
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Event::ExecFlow provides a ligh level API for defining complex flow controls
|
||||
Event::ExecFlow provides a high level API for defining complex flow controls
|
||||
with asynchronous execution of external programs.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Event-ExecFlow/
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
ExtUtils::XSBuilder is a set modules to parse C header files and create XS
|
||||
glue code and documentation out of it. Idealy this allows to "write" an
|
||||
glue code and documentation out of it. Ideally this allows to "write" an
|
||||
interface to a C library without coding a line. Since no C-API is ideal,
|
||||
some adjuments are necessary most of the time. So to use this module you
|
||||
must still be familar with C and XS programming, but it removes a lot of
|
||||
some adjustments are necessary most of the time. So to use this module you
|
||||
must still be familiar with C and XS programming, but it removes a lot of
|
||||
stupid work and copy&paste from you. Also when the C API changes, most
|
||||
of the time you only have to rerun XSBuilder to get your new Perl API.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This module is used to work with .desktop files. The format of these files is
|
||||
specified by the freedesktop "Desktp Entry" specification.
|
||||
specified by the freedesktop "Desktop Entry" specification.
|
||||
|
||||
WWW: http://search.cpan.org/dist/File-DesktopEntry/
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ File::Find::Object does same job as File::Find but works like an
|
|||
object and with an iterator. As File::Find is not object oriented, one
|
||||
cannot perform multiple searches in the same application. The second
|
||||
problem of File::Find is its file processing: after starting its main
|
||||
loop, one cannot easilly wait for another event an so get the next
|
||||
loop, one cannot easily wait for another event an so get the next
|
||||
result.
|
||||
|
||||
With File::Find::Object you can get the next file by calling the
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ filesystem in which directories do not exist. It provides an
|
|||
abstraction over any normal filesystem which makes it appear as if
|
||||
directories do not exist. In effect, it will automatically create
|
||||
directories as needed. This is create for things like install scripts
|
||||
and such, as you never need to worry about the existance of directories,
|
||||
and such, as you never need to worry about the existence of directories,
|
||||
just write to a file, no matter where it is.
|
||||
|
||||
WWW: http://search.cpan.org/dist/File-Flat/
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ For this module shared-mime-info-spec 0.12 was used.
|
|||
This package only uses the globs file. No real magic checking is
|
||||
used. The File::MimeInfo::Magic package is provided for magic typing.
|
||||
|
||||
If you want to detemine the mimetype of data in a memory buffer
|
||||
If you want to determine the mimetype of data in a memory buffer
|
||||
you should use File::MimeInfo::Magic in combination with IO::Scalar.
|
||||
|
||||
WWW: http://search.cpan.org/dist/File-MimeInfo/
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
File::NCopy::copy copies files to directories, or a single file to
|
||||
another file. You can also use a reference to a file handle if you wish
|
||||
whem doing a file to file copy. The functionality is very similar to
|
||||
when doing a file to file copy. The functionality is very similar to
|
||||
cp. If the argument is a directory to directory copy and the recursive
|
||||
flag is set then it is done recursively like cp -R. In fact it behaves
|
||||
like cp on Unix for the most part.
|
||||
|
||||
If called in array context, an array of successful copies is returned,
|
||||
otherwise the number of succesful copies is returned. If passed a file
|
||||
otherwise the number of successful copies is returned. If passed a file
|
||||
handle, it's difficult to make sure the file we are copying isn't the
|
||||
same that we are copying to, since by opening the file in write mode it
|
||||
gets pooched. To avoid this use file names instead, if at all possible,
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
This module simplifies the routine job of selecting a random file. (As you
|
||||
can find at CGI scripts). It's done, because it's boring (and
|
||||
errorprone), always to write something like
|
||||
error prone), always to write something like
|
||||
|
||||
my @files = (<*.*>);
|
||||
my $randf = $files[rand @files];
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ of files and directories.
|
|||
is_deeply( slurp_tree( "t/some_path" ), { foo => {}, bar => "sample\n" },
|
||||
"some_path contains a directory called foo, and a file bar" );
|
||||
|
||||
The tree datastructure is a hash of hashes. The keys of each hash are
|
||||
The tree data structure is a hash of hashes. The keys of each hash are
|
||||
names of directories or files. Directories have hash references as
|
||||
their value, files have a scalar which holds the contents of the file.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
The File::Tail module is designed for reading files which are continously
|
||||
appended to (the name comes from the tail -f directive). Usualy such files
|
||||
are logfiles of some description.
|
||||
The File::Tail module is designed for reading files which are continuously
|
||||
appended to (the name comes from the tail -f directive). Usually such files
|
||||
are log files of some description.
|
||||
|
||||
WWW: http://search.cpan.org/dist/File-Tail/
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
Converts data to/from stringified form, appropriate for
|
||||
saving-to/reading-from permanent storage.
|
||||
|
||||
Deals with objects, circular lists, repeated appearence of
|
||||
Deals with objects, circular lists, repeated appearance of
|
||||
the same refence. Does not deal with overloaded stringify
|
||||
operator yet.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This module provides an interface to (most of) the functions available
|
||||
in the popt library. See the popt(3) manpage for more details about
|
||||
in the popt library. See the popt(3) man page for more details about
|
||||
what the popt library can do.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Getopt-Popt/
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ IO::Null
|
|||
========
|
||||
|
||||
Calling a constructor of this class always succeeds, returning a new
|
||||
null filehabdle. Writing to any object of this class is always a no-
|
||||
null filehandle. Writing to any object of this class is always a no-
|
||||
operation, and returns true. Reading from any object of this class is
|
||||
always nooperation, and returns empty-string or empty-list, as
|
||||
appropriate.
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
IO::Toolkit - Perl extension to create logfiles
|
||||
IO::Toolkit - Perl extension to create log files
|
||||
|
||||
WWW: http://search.cpan.org/dist/IO-Toolkit
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This module implements a FIFO queueing infrastructure, using a directory
|
||||
This module implements a FIFO queuing infrastructure, using a directory
|
||||
as the communications and storage media. No daemon process is required
|
||||
to manage the queue; all communication takes place via the filesystem.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ IPC::MM provides an interface to Ralf Engelschall's mm library, allowing
|
|||
memory to be shared between multiple processes in a relatively
|
||||
convenient way.
|
||||
|
||||
IPC::MM provides methods to create and destoy shared memory segments and
|
||||
IPC::MM provides methods to create and destroy shared memory segments and
|
||||
to access data structures within those shared memory segments, as well
|
||||
as miscellaneous methods. Additionally, it provides a tied interface
|
||||
for scalars and hashes.
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ easy to share the contents of that variable with other Perl processes.
|
|||
Currently either scalars or hashes can be tied; tying of arrays remains
|
||||
a work in progress. However, the variable being tied may contain
|
||||
arbitrarily complex data structures - including references to arrays,
|
||||
hashes of hashes, etc. See the "REFERENCES" entry in this manpage below
|
||||
hashes of hashes, etc. See the "REFERENCES" entry in this man page below
|
||||
for more information.
|
||||
|
||||
WWW: http://search.cpan.org/dist/IPC-Shareable/
|
||||
|
|
|
|||
|
|
@ -2,10 +2,10 @@ This module provides a shared memory cache accessed as a
|
|||
tied hash.
|
||||
Shared memory is an area of memory that is available to
|
||||
all processes. It is accessed by choosing a key, the
|
||||
ipc_key arguement to tie. Every process that accesses
|
||||
ipc_key argument to tie. Every process that accesses
|
||||
shared memory with the same key gets access to the same
|
||||
region of memory. In some ways it resembles a file
|
||||
system, but it is not hierarchical and it is resident in
|
||||
memory. This makes it harder to use than a filesystem but
|
||||
much faster. The data in shared memory persists until the
|
||||
machine is rebooted or it is explicitely deleted.
|
||||
machine is rebooted or it is explicitly deleted.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ An "iterator" is an object, represented as a code block that generates the
|
|||
you need a value to operate on, you pull it from the iterator. If it
|
||||
depends on other iterators, it pulls values from them when it needs to.
|
||||
Iterators can be chained together (see Iterator::Util for functions that
|
||||
help you do just that), queueing up work to be done but not actually doing
|
||||
help you do just that), queuing up work to be done but not actually doing
|
||||
it until a value is needed at the front end of the chain. At that time,
|
||||
one data value is pulled through the chain.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ every aspect of Lexical::Persistence's behavior.
|
|||
|
||||
Lexical::Persistence lets your code access persistent data through lexical
|
||||
variables. This example prints "some value" because the value of $x
|
||||
perists in the $lp object between setter() and getter().
|
||||
persists in the $lp object between setter() and getter().
|
||||
|
||||
use Lexical::Persistence;
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This module permits from perl to the gettext() family of functions
|
||||
for retreiving message strings from databases constructed to
|
||||
for retrieving message strings from databases constructed to
|
||||
internationalize software.
|
||||
|
||||
--Dima.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
This module make use of Algorithm::Accounting and SVK to do
|
||||
simple accounting of any SVK repository. The installed
|
||||
svn-accounting.pl script demostrate a simple use to this module,
|
||||
svn-accounting.pl script demonstrate a simple use to this module,
|
||||
you may try:
|
||||
|
||||
svk-accounting.pl //
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
This module make use of Algorithm::Accounting and SVN::Log to do
|
||||
simple accounting of any subversion repository (not necessarily
|
||||
local, as long as you can do "svn log" to). The installed
|
||||
svn-accounting.pl script demostrate a simple use to this module,
|
||||
svn-accounting.pl script demonstrate a simple use to this module,
|
||||
you may try:
|
||||
|
||||
svn-accounting.pl http://svn.collab.net/repos/svn/
|
||||
|
|
|
|||
|
|
@ -1,12 +1,12 @@
|
|||
The Log::Agent module provides an abstract layer for logging and tracing, which
|
||||
is independant from the actual method used to physically perform those
|
||||
is independent from the actual method used to physically perform those
|
||||
activities. It acts as an agent (hence the name) that collects the requests and
|
||||
delegates processing to a sublayer: the logging driver.
|
||||
|
||||
The Log::Agent module is meant to be used in all reusable components, since
|
||||
they cannot know in advance how the application which ends up using them will
|
||||
perform its logging activities: either by emitting messages on stdout and
|
||||
errors on stderr, or by directing messages to logfiles, or by using syslog(3).
|
||||
errors on stderr, or by directing messages to log files, or by using syslog(3).
|
||||
|
||||
The logging interface is common for all the logging drivers, and is therefore
|
||||
the result of a compromise between many logging schemes: any information given
|
||||
|
|
@ -14,7 +14,7 @@ at this level must be either handled by all drivers, or may be ignored
|
|||
depending on the application's final choice.
|
||||
|
||||
WARNING: THIS INTERFACE IS STILL SOMEWHAT ALPHA AND COULD STILL CHANGE
|
||||
DEPENDING ON THE FEEDBACK THE AUTHOR RECIEVES, WITHOUT ANY BACKWARD
|
||||
DEPENDING ON THE FEEDBACK THE AUTHOR RECEIVES, WITHOUT ANY BACKWARD
|
||||
COMPATIBILITY ASSURANCE.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Log-Agent/
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Log::Dispatch::Config is a subclass of Log::Dispatch and provides a
|
||||
way to configure Log::Dispatch object with configulation file
|
||||
way to configure Log::Dispatch object with configuration file
|
||||
(default, in AppConfig format). This is almost a log4j equivalent for
|
||||
Perl, not with all API compatibility though.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ a timestamp and a stack trace, but some can be filled in by the user, like
|
|||
a tag by which to identify it or group it, and a level at which to handle
|
||||
the message (for example, log it, or die with it)
|
||||
|
||||
Log::Message also provides a powerfull way of searching through items by
|
||||
Log::Message also provides a powerful way of searching through items by
|
||||
regexes on messages, tags and level.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Log-Message
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
Perl module to rotate logfiles
|
||||
Perl module to rotate log files
|
||||
|
||||
Author: Paul Gampe <pgampe@users.sourceforge.net>
|
||||
WWW: http://search.cpan.org/dist/Logfile-Rotate/
|
||||
|
|
|
|||
|
|
@ -3,6 +3,6 @@ this is keyed on perl version as indicated in $]. The second level hash
|
|||
is module => version pairs.
|
||||
|
||||
It also contains %Module::CoreList::released hash, which has ISO formatted
|
||||
versions of the release dates, as gleaned from the perlhist manpage.
|
||||
versions of the release dates, as gleaned from the perlhist man page.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Module-CoreList/
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ using the inside-out object model.
|
|||
This module implements inside-out objects as anonymous scalar references that
|
||||
are blessed into a class with the scalar containing the ID for the object
|
||||
(usually a sequence number). For Perl 5.8.3 and later, the scalar reference is
|
||||
set as readonly to prevent accidental modifications to the ID. Object data
|
||||
set as read-only to prevent accidental modifications to the ID. Object data
|
||||
(i.e., fields) are stored within the class's package in either arrays indexed
|
||||
by the object's ID, or hashes keyed to the object's ID.
|
||||
|
||||
|
|
|
|||
|
|
@ -4,6 +4,6 @@ order to allow your objects to generate unique cryptographic signatures.
|
|||
The method used to generate the signature is based on Storable and
|
||||
Digest::MD5. The object is fed to Storable::nfreeze to get a string,
|
||||
which is then passed to Digest::MD5::md5_hex to get a unique 32
|
||||
character hexidecimal signature.
|
||||
character hexadecimal signature.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Object-Signature/
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ cross-platform packaging and deployment a breeze for Perl programmers.
|
|||
Notable features include:
|
||||
|
||||
* Turn your Perl programs into ready-to-run executables
|
||||
* Pack scripts and requered libraries with a binary loader
|
||||
* Pack scripts and required libraries with a binary loader
|
||||
* Put PAR files into @INC to avoid version conflicts
|
||||
* Works with remote URL as well as local files
|
||||
* Supports XS modules and DATA sections
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
From the website:-
|
||||
|
||||
This library allows to intercate with a smart card and pcsc-lite using the
|
||||
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.
|
||||
|
||||
WWW: http://ludovic.rousseau.free.fr/softwares/pcsc-perl/
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ whenever the code decides to bail out by die'ing.) If the signal handler
|
|||
returns 1 (as in the example above), POE will assume that the handler
|
||||
dealt with the signal appropriately. If the signal handler returns 0,
|
||||
POE will assume that the handler does not want to deal with the signal
|
||||
and POE will propgate the exception as if the handler never existed.
|
||||
and POE will propagate the exception as if the handler never existed.
|
||||
|
||||
Caveat: POE::Exceptions will die on its own in the case of a double
|
||||
exception fault. If the DIE signal handler itself throws an exception,
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
This program turns ordinary perl scripts into long running daemons, making
|
||||
subsequent executions extremely fast. It forks several processes for each
|
||||
script, allowing many proceses to call the script at once.
|
||||
script, allowing many processes to call the script at once.
|
||||
|
||||
WWW: http://search.cpan.org/dist/PPerl/
|
||||
|
|
|
|||
|
|
@ -5,11 +5,11 @@ I needed a basic text-mode GUI framework to implement some
|
|||
nice-looking proggies on Linux. Didn't find any around, so necessity
|
||||
became the mother of PerlVision. And this beast kept growing as I made
|
||||
love to Perl, so now it's far from 'basic'. Provides 90% of the
|
||||
features you'd want for a user interface, including checkboxes,
|
||||
radiobuttons, three different styles (!) of pushbuttons, single and
|
||||
multiple selection listboxes, an extensible editbox that does
|
||||
autowrapping, a scrollable viewbox, single line text entry fields, a
|
||||
menubar with pulldown menus, and full popup dialog boxes with multiple
|
||||
features you'd want for a user interface, including check boxes,
|
||||
radio buttons, three different styles (!) of pushbuttons, single and
|
||||
multiple selection list boxes, an extensible edit box that does
|
||||
auto-wrapping, a scrollable viewbox, single line text entry fields, a
|
||||
menu bar with pulldown menus, and full pop-up dialog boxes with multiple
|
||||
controls.
|
||||
|
||||
This version of PerlVision uses Will Setzer's Curses.pm dynaload
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
Package::Constants lists all the constants defined in a certain package.
|
||||
This can be useful for, among others, setting up an autogenerated
|
||||
This can be useful for, among others, setting up an auto-generated
|
||||
@EXPORT/@EXPORT_OK for a Constants.pm file.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Package-Constants
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
The Parse::Lex.pm module for perl5 is an object-oriented generator of
|
||||
lexical analyzers.
|
||||
|
||||
This distribution includes Parse::YYLex (writed by Vladimir Alexiev)
|
||||
This distribution includes Parse::YYLex (written by Vladimir Alexiev)
|
||||
a lexer generator that you can use with yacc parsers.
|
||||
|
||||
WWW: http://search.cpan.org/dist/ParseLex/
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ This module is a first crack at providing a consistent interface to
|
|||
Unix (and maybe other multitasking OS's) process table information.
|
||||
The impetus for this came about with my frustration at having to parse
|
||||
the output of various systems' ps commands to check whether specific
|
||||
processes were running on different boxes at a larged mixed Unix site.
|
||||
processes were running on different boxes at a large mixed Unix site.
|
||||
The output format of ps was different on each OS, and sometimes
|
||||
changed with each new release of an OS. Also, running a ps subprocess
|
||||
from within a perl or shell script and parsing the output was not a
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ functionality of the backticks operator and system() functions,
|
|||
plus many uses of fork/exec, open2() and open3(). Proc::Reliable
|
||||
incorporates a number of options, including sending data to the
|
||||
subprocess on STDIN, collecting STDOUT and STDERR separately or
|
||||
together, killing hung processes, timouts and automatic retries.
|
||||
together, killing hung processes, timeouts and automatic retries.
|
||||
|
||||
WWW: http://search.cpan.org/dist/Proc-Reliable/
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@ This is a second go at a module to simplify installing die() and warn()
|
|||
handlers, and to make such handlers easier to write and control.
|
||||
|
||||
For most people, this just means that if use Religion; then you'll get
|
||||
noticably better error reporting from warn() and die(). This is especially
|
||||
noticeably better error reporting from warn() and die(). This is especially
|
||||
useful if you are using eval().
|
||||
|
||||
Religion provides four classes, WarnHandler, DieHandler, WarnPreHandler, and
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ quantities or attributes of interest.
|
|||
Resources can be loaded from or saved to resource files. Methods are
|
||||
provided to search, modify and create resources. Packages use resources to
|
||||
hardwire in their code the default values for their attributes, along with
|
||||
documentation for the attibutes themselves.
|
||||
documentation for the attributes themselves.
|
||||
|
||||
Packages inherit resources when subclassed, and the resource names are
|
||||
updated dynamically to reflect a class hierarchy.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
This module is intented to do some Social Security Number validation
|
||||
This module is intended to do some Social Security Number validation
|
||||
(not verification) beyond just seeing if it contains 9 digits and isn't
|
||||
all 0s. The data is taken from the Social Security Admin. website,
|
||||
specifically:
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
SVN::ACL is a simple fronend to make the svnserve.conf, passwd,
|
||||
SVN::ACL is a simple frontend to make the svnserve.conf, passwd,
|
||||
authz for Subversion.
|
||||
|
||||
After subversion 1.3.0, it offers the new access control for
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
S4 provides a wrapper to subversion that extends several of the commands
|
||||
(for example, "fixprop", "scrub", "snapshot"). It understands all svn
|
||||
commands; you may simply use "s4" whereever you would normally type
|
||||
commands; you may simply use "s4" wherever you would normally type
|
||||
"svn".
|
||||
|
||||
WWW: http://search.cpan.org/dist/SVN-S4/
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Reference in a new issue