Ports Search

strictures turns on indirect checking only when it thinks it's running in a compilation (or pod coverage) test - though if this causes undesired behaviour this can be overriden by setting the PERL_STRICTURES_EXTRA environment variable.

subatom is a small script to produce an Atom feed from subversion commits. You can use this with a feed reader to see new commits to your repository.

Subversion is a version control system designed to be as similar to cvs(1) as possible, while fixing many outstanding problems with cvs(1). This port adds Perl bindings to Subversion.

The SMV (Symbolic Model Verifier) system is a tool for checking finite state systems against specifications in the temporal logic CTL (Computational Tree Logic). One specifies the finite state system (finite automaton, Mealy machine, full adder circuit, ..) as a Kripke structure in the SMV language and provides specifications in CTL. The model checking algorithm allows to determine if the Kripke structure fulfills the specifications.

Allows you to both load one or more modules, while setting up inheritance from those modules at the same time. If a module in the import list is followed by something that doesn't look like a legal module name, the VERSION method will be called with it as an argument.

Extension of the Horde_Autoloader that implements caching of class-file-maps. The caching method is determined automatically from the list of supported cache backends: APC, XCache, eAccelerator, local file system.

This module activates community provided syntax extensions to Perl. You pass it a feature name, and optionally a scalar with arguments, and the dispatching system will load and install the extension in your package. The import arguments are parsed with Data::OptList(3). There are no standardised options. Please consult the documentation for the specific syntax feature to find out about possible configuration options.

By default, variables are private to each thread, and each newly created thread gets a private copy of each existing variable. This module allows you to share variables across different threads (and pseudoforks on Win32). It is used together with the threads module.

Perl 5.6 introduced something called interpreter threads. Interpreter threads are different from 5005threads (the thread model of Perl 5.005) by creating a new Perl interpreter per thread, and not sharing any data or state between threads by default. Prior to Perl 5.8, this has only been available to people embedding Perl, and for emulating fork() on Windows. The threads API is loosely based on the old Thread.pm API. It is very important to note that variables are not shared between threads, all variables are by default thread local. To use shared variables one must use threads::shared. It is also important to note that you must enable threads by doing use threads as early as possible in the script itself, and that it is not possible to enable threading inside an eval "", do, require, or use. In particular, if you are intending to share variables with threads::shared, you must use threads before you use threads::shared. (threads will emit a warning if you do it the other way around.)

Perl's require builtin (and its use wrapper) requires the files it loads to return a true value. This is usually accomplished by placing a single 1; statement at the end of included scripts or modules. It's not onerous to add but it's a speed bump on the Perl novice's road to enlightenment. In addition, it appears to be a non-sequitur to the uninitiated, leading some to attempt to mitigate its appearance with a comment: 1; # keep require happy or: 1; # Do not remove this line or even: 1; # Must end with this, because Perl is bogus. This module packages this "return true" behaviour so that it need not be written explicitly. It can be used directly, but it is intended to be invoked from the import method of a Modern::Perl-style module that enables modern Perl features and conveniences and cleans up legacy Perl warts.