ARGV The special filehandle that iterates over command-line filenames in @ARGV . Usually written as the null filehandle in the angle operator <> . Note that currently ARGV only has its magical effect within the <> operator; elsewhere it is just a plain filehandle corresponding to the last file opened by <> . In particular, passing \*ARGV as a parameter to a function that expects a filehandle may not cause your function to automatically read the contents of all the files in @A

NAME SYNOPSIS DESCRIPTIONAccessors MethodsArchive::Tar::File->new( file => $path ) Archive::Tar::File->new( data => $path, $data, $opt ) Archive::Tar::File->new( chunk => $chunk ) $bool = $file->extract( [ $alternative_name ] ) $path = $file->full_path $bool = $file->validate $bool = $file->has_content $content = $file->get_content $cref = $file->get_content_by_ref $bool = $file->replace_content( $content ) $bool = $file->rename( $new_name ) $bool = $

NAME SYNOPSIS DESCRIPTION Object MethodsArchive::Tar->new( [$file, $compressed] ) $tar->read ( $filename|$handle, [$compressed, {opt => 'val'}] ) $tar->contains_file( $filename ) $tar->extract( [@filenames] ) $tar->extract_file( $file, [$extract_path] ) $tar->list_files( [\@properties] ) $tar->get_files( [@filenames] ) $tar->get_content( $file ) $tar->replace_content( $file, $content ) $tar->rename( $file, $new_name ) $tar->chmod( $file, $mode ) $tar->cho

NAME VERSION DESCRIPTION SYNOPSIS METHODSClass Methods Instance Methods NAME App::Prove::State::Result::Test - Individual test results. VERSION Version 3.35 DESCRIPTION The prove command supports a --state option that instructs it to store persistent state across runs. This module encapsulates the results for a single test. SYNOPSIS # Re-run failed tests $ prove --state=failed,save -rbv METHODS Class Methods new Instance Methods name The name of the test. Usually a filename. elapsed

NAME VERSION DESCRIPTION SYNOPSIS METHODSClass Methods state_version test_class NAME App::Prove::State::Result - Individual test suite results. VERSION Version 3.35 DESCRIPTION The prove command supports a --state option that instructs it to store persistent state across runs. This module encapsulates the results for a single test suite run. SYNOPSIS # Re-run failed tests $ prove --state=failed,save -rbv METHODS Class Methods new my $result = App::Prove::State::Result->new({ gener

NAME VERSION DESCRIPTION SYNOPSIS METHODSClass Methods result_class extensions results commit Instance Methods NAME App::Prove::State - State storage for the prove command. VERSION Version 3.35 DESCRIPTION The prove command supports a --state option that instructs it to store persistent state across runs. This module implements that state and the operations that may be performed on it. SYNOPSIS # Re-run failed tests $ prove --state=failed,save -rbv METHODS Class Methods new Accepts a has

NAME VERSION DESCRIPTION SYNOPSIS METHODSClass Methods Attributes PLUGINSSample Plugin SEE ALSO NAME App::Prove - Implements the prove command. VERSION Version 3.35 DESCRIPTION Test::Harness provides a command, prove , which runs a TAP based test suite and prints a report. The prove command is a minimal wrapper around an instance of this module. SYNOPSIS use App::Prove; my $app = App::Prove->new; $app->process_args(@ARGV); $app->run; METHODS Class Methods new Create a new App:

NAME SYNOPSIS DESCRIPTIONDBM Comparisons SEE ALSO NAME AnyDBM_File - provide framework for multiple DBMs NDBM_File, DB_File, GDBM_File, SDBM_File, ODBM_File - various DBM implementations SYNOPSIS use AnyDBM_File; DESCRIPTION This module is a "pure virtual base class"--it has nothing of its own. It's just there to inherit from one of the various DBM packages. It prefers ndbm for compatibility reasons with Perl 4, then Berkeley DB (See DB_File), GDBM, SDBM (which is always there--it comes wit

and These operators are documented in perlop.

alarm SECONDS alarm Arranges to have a SIGALRM delivered to this process after the specified number of wallclock seconds has elapsed. If SECONDS is not specified, the value stored in $_ is used. (On some machines, unfortunately, the elapsed time may be up to one second less or more than you specified because of how seconds are counted, and process scheduling may delay the delivery of the signal even further.) Only one timer may be counting at once. Each call disables the previous timer, and an