Ports 搜索

Description from the home page: Devel::LexAlias provides the ability to alias a lexical variable in a subroutines scope to one of your choosing. If you don't know why you'd want to do this, I'd suggest that you skip this module. If you think you have a use for it, I'd insist on it. Still here? lexalias( $where, $name, $variable ) $where refers to the subroutine in which to alias the lexical, it can be a coderef or a call level such that you'd give to caller $name is the name of the lexical within that subroutine $variable is a reference to the variable to install at that location

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 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/response interfaces to the monitored applications, etc.

Devel::CallChecker makes some new features of the Perl 5.14.0 C API available to XS modules running on older versions of Perl. The features are centred around the function cv_set_call_checker, which allows XS code to attach a magical annotation to a Perl subroutine, resulting in resolvable calls to that subroutine being mutated at compile time by arbitrary C code. This module makes cv_set_call_checker and several supporting functions available. (It is possible to achieve the effect of cv_set_call_checker from XS code on much earlier Perl versions, but it is painful to achieve without the centralised facility.) Devel::CallCheckerprovides the implementation of the functions at runtime (on Perls where they are not provided by the core). It also, at compile time, supplies the C header file and link library which provide access to the functions. In normal use, "callchecker0_h" and "callchecker_linkable" should be called at build time (not authoring time) for the module that wishes to use the C functions.

Devel::NYTProf is a powerful feature-rich perl source code profiler. * Performs per-line statement profiling for fine detail * Performs per-subroutine statement profiling for overview * Performs per-block statement profiling (the first profiler to do so) * Accounts correctly for time spent after calls return * Performs inclusive and exclusive timing of subroutines * Subroutine times are per calling location (a powerful feature) * Can profile compile-time activity, just run-time, or just END time * Uses novel techniques for efficient profiling * Sub-microsecond (100ns) resolution on systems with clock_gettime() * Very fast - the fastest statement and subroutine profilers for perl * Handles applications that fork, with no performance cost * Immune from noise caused by profiling overheads and I/O * Program being profiled can stop/start the profiler * Generates richly annotated and cross-linked html reports * Trivial to use with mod_perl - add one line to httpd.conf * Includes an extensive test suite * Tested on very large codebases

This module profiles POE programs, in the same way the Devel::DProf family of modules do.

Perl module to patch perl source

This module attempts to generate a stack dump from a core file by locating the best available debugger (if any) and running it with the appropriate arguments and command script.

This is a simple developer's tool for finding circular references in objects and other types of references. Because of Perl's reference-count based memory management, circular references will cause memory leaks.

Given a list of Perl modules/filenames, this module makes require and use statements fail (no matter the specified files/modules are installed or not).

Figure out the names of variables passed into subroutines.