$] The revision, version, and subversion of the Perl interpreter, represented as a decimal of the form 5.XXXYYY, where XXX is the version / 1e3 and YYY is the subversion / 1e6. For example, Perl v5.10.1 would be "5.010001". This variable can be used to determine whether the Perl interpreter executing a script is in the right range of versions: warn "No PerlIO!\n" if $] lt '5.008'; When comparing $] , string comparison operators are highly recommended. The inherent limitations of binary floati

SYNOPSIS DESCRIPTION AUTHOR SYNOPSIS use Config::Extensions '%Extensions'; if ($Extensions{PerlIO::via}) { # This perl has PerlIO::via built } DESCRIPTION The Config::Extensions module provides a hash %Extensions containing all the core extensions that were enabled for this perl. The hash is keyed by extension name, with each entry having one of 3 possible values: dynamic The extension is dynamically linked nonxs The extension is pure perl, so doesn't need linking to the perl executab

NAME SYNOPSIS DESCRIPTION NAME vars - Perl pragma to predeclare global variable names SYNOPSIS use vars qw($frob @mung %seen); DESCRIPTION NOTE: For use with variables in the current package for a single scope, the functionality provided by this pragma has been superseded by our declarations, available in Perl v5.6.0 or later, and use of this pragma is discouraged. See our. This will predeclare all the variables whose names are in the list, allowing you to use them under "use strict", and di

state VARLIST state TYPE VARLIST state VARLIST : ATTRS state TYPE VARLIST : ATTRS state declares a lexically scoped variable, just like my. However, those variables will never be reinitialized, contrary to lexical variables that are reinitialized each time their enclosing block is entered. See Persistent Private Variables in perlsub for details. If more than one variable is listed, the list must be placed in parentheses. With a parenthesised list, undef can be used as a dummy placeholder. Howev

ARGVOUT The special filehandle that points to the currently open output file when doing edit-in-place processing with -i. Useful when you have to do a lot of inserting and don't want to keep modifying $_ . See perlrun for the -i switch.

NAME SYNOPSIS DESCRIPTION AUTHOR LICENSE NAME CPAN::Kwalify - Interface between CPAN.pm and Kwalify.pm SYNOPSIS use CPAN::Kwalify; validate($schema_name, $data, $file, $doc); DESCRIPTION _validate($schema_name, $data, $file, $doc) $schema_name is the name of a supported schema. Currently only distroprefs is supported. $data is the data to be validated. $file is the absolute path to the file the data are coming from. $doc is the index of the document within $doc that is to be validated. The

NAME SYNOPSIS DESCRIPTION NAME ExtUtils::MM_MacOS - once produced Makefiles for MacOS Classic SYNOPSIS # MM_MacOS no longer contains any code. This is just a stub. DESCRIPTION Once upon a time, MakeMaker could produce an approximation of a correct Makefile on MacOS Classic (MacPerl). Due to a lack of maintainers, this fell out of sync with the rest of MakeMaker and hadn't worked in years. Since there's little chance of it being repaired, MacOS Classic is fading away, and the code was icky t

NAME VERSION SYNOPSIS DESCRIPTION METHODSClass Methods Instance Methods See Also NAME TAP::Parser::Multiplexer - Multiplex multiple TAP::Parsers VERSION Version 3.35 SYNOPSIS use TAP::Parser::Multiplexer; my $mux = TAP::Parser::Multiplexer->new; $mux->add( $parser1, $stash1 ); $mux->add( $parser2, $stash2 ); while ( my ( $parser, $stash, $result ) = $mux->next ) { # do stuff } DESCRIPTION TAP::Parser::Multiplexer gathers input from multiple TAP::Parsers. Internally it call

NAME DESCRIPTION AUTHOR SEE ALSO NAME ExtUtils::CBuilder::Platform::Windows - Builder class for Windows platforms DESCRIPTION This module implements the Windows-specific parts of ExtUtils::CBuilder. Most of the Windows-specific stuff has to do with compiling and linking C code. Currently we support the 3 compilers perl itself supports: MSVC, BCC, and GCC. This module inherits from ExtUtils::CBuilder::Base , so any functionality not implemented here will be implemented there. The interfaces ar

NAME NAME Encode::JP::JIS7 -- internally used by Encode::JP