Ports Search

The Inline::Python module allows you to put Python source code directly "inline" in a Perl script or module. It sets up an in-process Python interpreter, runs your code, and then examines Python's symbol table for things to bind to Perl. The process of interrogating the Python interpreter for globals only occurs the first time you run your Python code. The namespace is cached, and subsequent calls use the cached version.

Arch is a really nifty revision control system. It's "whole-tree changeset based" which means, roughly, that it can handle (with atomic commits) file and directory adds, deletes, and renames cleanly, and that it does branching simply and easily. Arch is also "distributed" which means, for example that you can make arch branches of your own from remote projects, even if you do not have write access to the revision control archives for those projects.

Module::Build::Convert - Makefile.PL to Build.PL converter ExtUtils::MakeMaker has been a de-facto standard for the common distribution of Perl modules; Module::Build is expected to supersede ExtUtils::MakeMaker in some time (part of the Perl core as of 5.10?) The transition takes place slowly, as the converting process manually achieved is yet an uncommon practice. The Module::Build::Convert Makefile.PL parser is intended to ease the transition process.

This module optimizes Moo type checks when used with Type::Tiny to perform better. It will automatically apply to isa checks and coercions that use Type::Tiny. Non-Type::Tiny isa checks will work as normal. This is done by inlining the type check in a more optimal manner that is specific to Type::Tiny rather than the general mechanism Moo usually uses. With this module, setters with type checks should be as fast as an equivalent check in Moose.

This module allows you to specify your project-wide or even company-wide Moose meta-policy. Most all of Moose's features can be customized through the use of custom metaclasses, however fiddling with the metaclasses can be hairy. Moose::Policy removes most of that hairiness and makes it possible to cleanly contain a set of meta-level customizations in one easy to use module.

Out of the box Moose only provides very barebones cloning support in order to maximize flexibility. This role provides a clone method that makes use of the low level cloning support already in Moose and adds selective deep cloning based on introspection on top of that. Attributes with the Clone trait will handle cloning of data within the object, typically delegating to the attribute value's own clone method.

OOTools is a collection of pragmas to easily create constructors methods and lvalue accessor methods at compile time. OOTools distribution includes: Class::constr Pragma to implement constructor methods Class::props Pragma to implement lvalue accessors with options Class::group Pragma to implement group of properties accessors with options Object::props Pragma to implement lvalue accessors with options Object::group Pragma to implement group of properties accessors with options

This module adds lightweight hooks into the inner workings of POE. Currently, one can add hooks into POE that get called before/after an event is dispatched and/or before/after a Session is created. These callbacks receive the exact same argument list as their Kernel/Session counterpart. For event dispatch related callbacks, see _dispatch_event in POE::Kernel. For session related callbacks, see create in POE::Session.

The most of the code of this module is taken from the PAUSE code as of April 2013 almost verbatim. Thus, the heart of this module should be quite stable. However, I made it not to use pipe ("-|") as well as I stripped database-related code. If you encounter any issue, that's most probably because of my modification. This module doesn't provide features to extract a distribution or parse meta files intentionally.

ReadonlyX combines the best features of p5-Readonly and p5-Readonly-XS, and is a drop-in replacement. It creates read-only scalars, arrays, and hashes. It was created by maintainer of Readonly itself. The author says: "ReadonlyX is the best of recent versions of Readonly without the old API and without the speed penalty of tie(...). It's what I'd like to do with Readonly if resolving bugs in it wouldn't break 16 years of code out there in Darkpan."