${^UTF8CACHE}

${^UTF8CACHE} This variable controls the state of the internal UTF-8 offset caching code. 1 for on (the default), 0 for off, -1 to debug the caching code by checking all its results against linear scans, and panicking on any discrepancy. This variable was added in Perl v5.8.9. It is subject to change or removal without notice, but is currently used to avoid recalculating the boundaries of multi-byte UTF-8-encoded characters.

die

die LIST die raises an exception. Inside an eval the error message is stuffed into $@ and the eval is terminated with the undefined value. If the exception is outside of all enclosing evals, then the uncaught exception prints LIST to STDERR and exits with a non-zero value. If you need to exit the process with a specific exit code, see exit. Equivalent examples: die "Can't cd to spool: $!\n" unless chdir '/usr/spool/news'; chdir '/usr/spool/news' or die "Can't cd to spool: $!\n" If the last ele

perlos2 - Perl under OS/2, DOS, Win0.3*, Win0.95 and WinNT.

NAME SYNOPSIS DESCRIPTIONTarget Other OSes Prerequisites Starting Perl programs under OS/2 (and DOS and...) Starting OS/2 (and DOS) programs under Perl Frequently asked questions"It does not work" I cannot run external programs I cannot embed perl into my program, or use _perl.dll_ from my program. `` and pipe-open do not work under DOS. Cannot start find.exe "pattern" file INSTALLATIONAutomatic binary installation Manual binary installation *Warning* Accessing documentationOS/2 _.INF_ f

perlopentut - simple recipes for opening files and pipes in Perl

NAME DESCRIPTION Opening Text FilesOpening Text Files for Reading Opening Text Files for Writing Opening Binary Files Opening Pipes Low-level File Opens via sysopen SEE ALSO AUTHOR and COPYRIGHT NAME perlopentut - simple recipes for opening files and pipes in Perl DESCRIPTION Whenever you do I/O on a file in Perl, you do so through what in Perl is called a filehandle. A filehandle is an internal name for an external file. It is the job of the open function to make the association between th

HANDLE->format_lines_per_page(EXPR)

HANDLE->format_lines_per_page(EXPR)

Attribute::Handlers - Simpler definition of attribute handlers

NAME VERSION SYNOPSIS DESCRIPTIONTyped lexicals Type-specific attribute handlers Non-interpretive attribute handlers Phase-specific attribute handlers Attributes as tie interfaces EXAMPLES UTILITY FUNCTIONS DIAGNOSTICS AUTHOR BUGS COPYRIGHT AND LICENSE NAME Attribute::Handlers - Simpler definition of attribute handlers VERSION This document describes version 0.97 of Attribute::Handlers. SYNOPSIS package MyClass; require 5.006; use Attribute::Handlers; no warnings 'redefine';

IO::Socket::UNIX - Object interface for AF_UNIX domain sockets

NAME SYNOPSIS DESCRIPTION CONSTRUCTOR METHODS SEE ALSO AUTHOR COPYRIGHT NAME IO::Socket::UNIX - Object interface for AF_UNIX domain sockets SYNOPSIS use IO::Socket::UNIX; my $SOCK_PATH = "$ENV{HOME}/unix-domain-socket-test.sock"; # Server: my $server = IO::Socket::UNIX->new( Type => SOCK_STREAM(), Local => $SOCK_PATH, Listen => 1, ); my $count = 1; while (my $conn = $server->accept()) { $conn->print("Hello " . ($count++) . "\n"); } # Client: my $client =

${^RE_DEBUG_FLAGS}

${^RE_DEBUG_FLAGS} The current value of the regex debugging flags. Set to 0 for no debug output even when the re 'debug' module is loaded. See re for details. This variable was added in Perl v5.10.0.

TAP::Formatter::Console::Session - Harness output delegate for default console output

NAME VERSION DESCRIPTION clear_for_close close_test header result NAME TAP::Formatter::Console::Session - Harness output delegate for default console output VERSION Version 3.35 DESCRIPTION This provides console orientated output formatting for TAP::Harness. clear_for_close close_test header result

Pod::Checker, podchecker() - check pod documents for syntax errors

NAME SYNOPSIS OPTIONS/ARGUMENTSpodchecker() DESCRIPTION DIAGNOSTICSErrors Warnings Hyperlinks RETURN VALUE EXAMPLES INTERFACE AUTHOR NAME Pod::Checker, podchecker() - check pod documents for syntax errors SYNOPSIS use Pod::Checker; $num_errors = podchecker($filepath, $outputpath, %options); my $checker = new Pod::Checker %options; $checker->parse_from_file($filepath, \*STDERR); OPTIONS/ARGUMENTS $filepath is the input POD to read and $outputpath is where to write POD syntax error mes