perlman gods <HR> <H1><A NAME="NAME">NAME</A></H1> perldelta - what's new for perl5.005 <HR> <H1><A NAME="DESCRIPTION">DESCRIPTION</A></H1> This document describes differences between the 5.004 release and this one. <HR> <H1><A NAME="About_the_new_versioning_system">About the new versioning system</A></H1> Perl is now developed on two tracks: a maintenance track that makes small, safe updates to released production versions with emphasis on compatibility; and a development track that pursues more aggressive evolution. Maintenance releases (which should be considered production quality) have subversion numbers that run from <CODE>1</CODE> to <CODE>49</CODE>, and development releases (which should be considered ``alpha'' quality) run from <CODE>50</CODE> to <CODE>99</CODE>. Perl 5.005 is the combined product of the new dual-track development scheme. <HR> <H1><A NAME="Incompatible_Changes">Incompatible Changes</A></H1> <HR> <H2><A NAME="WARNING_This_version_is_not_bin">WARNING: This version is not binary compatible with Perl 5.004.</A></H2> Starting with Perl 5.004_50 there were many deep and far-reaching changes to the language internals. If you have dynamically loaded extensions that you built under perl 5.003 or 5.004, you can continue to use them with 5.004, but you will need to rebuild and reinstall those extensions to use them 5.005. See the INSTALL manpage for detailed instructions on how to upgrade. <HR> <H2><A NAME="Default_installation_structure_h">Default installation structure has changed</A></H2> The new Configure defaults are designed to allow a smooth upgrade from 5.004 to 5.005, but you should read the INSTALL manpage for a detailed discussion of the changes in order to adapt them to your system. <HR> <H2><A NAME="Perl_Source_Compatibility">Perl Source Compatibility</A></H2> When none of the experimental features are enabled, there should be very few user-visible Perl source compatibility issues. If threads are enabled, then some caveats apply. <CODE>@_</CODE> and <CODE>$_</CODE> become lexical variables. The effect of this should be largely transparent to the user, but there are some boundary conditions under which user will need to be aware of the issues. For example, [perlfunc:local|local(@_)] results in a ``Can't localize lexical variable <CODE>@_</CODE> ...'' message. This may be enabled in a future version. Some new keywords have been introduced. These are generally expected to have very little impact on compatibility. See <A HREF="#New_C_INIT_keyword">New <CODE>INIT</CODE> keyword</A>, <A HREF="#New_C_lock_keyword">New <CODE>lock</CODE> keyword</A>, and <A HREF="#New_C_qr_operator">New <A HREF="perlop.html#item_qr">qr</A> operator</A>. Certain barewords are now reserved. Use of these will provoke a warning if you have asked for them with the <CODE>-w</CODE> switch. See <A HREF="#C_our_is_now_a_reserved_word"><CODE>our</CODE> is now a reserved word</A>. <HR> <H2><A NAME="C_Source_Compatibility">C Source Compatibility</A></H2> There have been a large number of changes in the internals to support the new features in this release. <DL> <DT><A NAME="item_Core">Core sources now require ANSI C compiler</A> <DD> An ANSI C compiler is now required to build perl. See INSTALL. <DT><A NAME="item_All">All Perl global variables must now be referenced with an explicit prefix</A> <DD> All Perl global variables that are visible for use by extensions now have a <CODE>PL_</CODE> prefix. New extensions should <CODE>not</CODE> refer to perl globals by their unqualified names. To preserve sanity, we provide limited backward compatibility for globals that are being widely used like <CODE>sv_undef</CODE> and <CODE>na</CODE> (which should now be written as [perlman:perlguts], [perlman:perlguts] etc.) If you find that your XS extension does not compile anymore because a perl global is not visible, try adding a <CODE>PL_</CODE> prefix to the global and rebuild. It is strongly recommended that all functions in the Perl API that don't begin with <CODE>perl</CODE> be referenced with a <CODE>Perl_</CODE> prefix. The bare function names without the <CODE>Perl_</CODE> prefix are supported with macros, but this support may cease in a future release. See [perlman:perlguts]. <DT><A NAME="item_Enabling">Enabling threads has source compatibility issues</A> <DD> Perl built with threading enabled requires extensions to use the new <CODE>dTHR</CODE> macro to initialize the handle to access per-thread data. If you see a compiler error that talks about the variable <CODE>thr</CODE> not being declared (when building a module that has XS code), you need to add <CODE>dTHR;</CODE> at the beginning of the block that elicited the error. The API function [perlman:perlguts] should be used instead of directly accessing perl globals as [perlman:perlguts]. The API call is backward compatible with existing perls and provides source compatibility with threading is enabled. See <A HREF="#API_Changes_for_more_information">API Changes for more information</A>. </DL> <HR> <H2><A NAME="Binary_Compatibility">Binary Compatibility</A></H2> This version is NOT binary compatible with older versions. All extensions will need to be recompiled. Further binaries built with threads enabled are incompatible with binaries built without. This should largely be transparent to the user, as all binary incompatible configurations have their own unique architecture name, and extension binaries get installed at unique locations. This allows coexistence of several configurations in the same directory hierarchy. See INSTALL. <HR> <H2><A NAME="Security_fixes_may_affect_compat">Security fixes may affect compatibility</A></H2> A few taint leaks and taint omissions have been corrected. This may lead to ``failure'' of scripts that used to work with older versions. Compiling with -DINCOMPLETE_TAINTS provides a perl with minimal amounts of changes to the tainting behavior. But note that the resulting perl will have known insecurities. Oneliners with the <CODE>-e</CODE> switch do not create temporary files anymore. <HR> <H2><A NAME="Relaxed_new_mandatory_warnings_i">Relaxed new mandatory warnings introduced in 5.004</A></H2> Many new warnings that were introduced in 5.004 have been made optional. Some of these warnings are still present, but perl's new features make them less often a problem. See <A HREF="#New_Diagnostics">New Diagnostics</A>. <HR> <H2><A NAME="Licensing">Licensing</A></H2> Perl has a new Social Contract for contributors. See Porting/Contract. The license included in much of the Perl documentation has changed. Most of the Perl documentation was previously under the implicit GNU General Public License or the Artistic License (at the user's choice). Now much of the documentation unambigously states the terms under which it may be distributed. Those terms are in general much less restrictive than the GNU GPL. See [perlman:perl|the perl manpage] and the individual perl man pages listed therein. <HR> <H1><A NAME="Core_Changes">Core Changes</A></H1> <HR> <H2><A NAME="Threads">Threads</A></H2> WARNING: Threading is considered an experimental feature. Details of the implementation may change without notice. There are known limitations and some bugs. These are expected to be fixed in future versions. See README.threads. <HR> <H2><A NAME="Compiler">Compiler</A></H2> WARNING: The Compiler and related tools are considered experimental. Features may change without notice, and there are known limitations and bugs. Since the compiler is fully external to perl, the default configuration will build and install it. The Compiler produces three different types of transformations of a perl program. The C backend generates C code that captures perl's state just before execution begins. It eliminates the compile-time overheads of the regular perl interpreter, but the run-time performance remains comparatively the same. The CC backend generates optimized C code equivalent to the code path at run-time. The CC backend has greater potential for big optimizations, but only a few optimizations are implemented currently. The Bytecode backend generates a platform independent bytecode representation of the interpreter's state just before execution. Thus, the Bytecode back end also eliminates much of the compilation overhead of the interpreter. The compiler comes with several valuable utilities. <CODE>B::Lint</CODE> is an experimental module to detect and warn about suspicious code, especially the cases that the <CODE>-w</CODE> switch does not detect. <CODE>B::Deparse</CODE> can be used to demystify perl code, and understand how perl optimizes certain constructs. <CODE>B::Xref</CODE> generates cross reference reports of all definition and use of variables, subroutines and formats in a program. <CODE>B::Showlex</CODE> show the lexical variables used by a subroutine or file at a glance. <CODE>perlcc</CODE> is a simple frontend for compiling perl. See <CODE>ext/B/README</CODE>, the B manpage, and the respective compiler modules. <HR> <H2><A NAME="Regular_Expressions">Regular Expressions</A></H2> Perl's regular expression engine has been seriously overhauled, and many new constructs are supported. Several bugs have been fixed. Here is an itemized summary: <DL> <DT><A NAME="item_Many">Many new and improved optimizations</A> <DD> Changes in the RE engine: <PRE> Unneeded nodes removed; Substrings merged together; New types of nodes to process (SUBEXPR)* and similar expressions quickly, used if the SUBEXPR has no side effects and matches strings of the same length; Better optimizations by lookup for constant substrings; Better search for constants substrings anchored by $ ; </PRE> Changes in Perl code using RE engine: <PRE> More optimizations to s/longer/short/; study() was not working; /blah/ may be optimized to an analogue of index() if $& $` $' not seen; Unneeded copying of matched-against string removed; Only matched part of the string is copying if $` $' were not seen; </PRE> <DT>Many bug fixes <DD> Note that only the major bug fixes are listed here. See Changes for others. <PRE> Backtracking might not restore start of $3. No feedback if max count for * or + on "complex" subexpression was reached, similarly (but at compile time) for {3,34567} Primitive restrictions on max count introduced to decrease a possibility of a segfault; (ZERO-LENGTH)* could segfault; (ZERO-LENGTH)* was prohibited; Long REs were not allowed; /RE/g could skip matches at the same position after a zero-length match; </PRE> <DT><A NAME="item_New">New regular expression constructs</A> <DD> The following new syntax elements are supported: <PRE> (?<=RE) (?<!RE) (?{ CODE }) (?i-x) (?i:RE) (?(COND)YES_RE|NO_RE) (?>RE) \z </PRE> <DT>New operator for precompiled regular expressions <DD> See New C<qr. <DT><A NAME="item_Other">Other improvements</A> <DD> <PRE> Better debugging output (possibly with colors), even from non-debugging Perl; RE engine code now looks like C, not like assembler; Behaviour of RE modifiable by `use re' directive; Improved documentation; Test suite significantly extended; Syntax [:^upper:] etc., reserved inside character classes; </PRE> <DT><A NAME="item_Incompatible">Incompatible changes</A> <DD> <PRE> (?i) localized inside enclosing group; $( is not interpolated into RE any more; /RE/g may match at the same position (with non-zero length) after a zero-length match (bug fix). </PRE> </DL> See [perlman:perlre|the perlre manpage] and [perlman:perlop|the perlop manpage]. <HR> <H2><A NAME="Improved_malloc_">Improved malloc()</A></H2> See banner at the beginning of <CODE>malloc.c</CODE> for details. <HR> <H2><A NAME="Quicksort_is_internally_implemen">Quicksort is internally implemented</A></H2> Perl now contains its own highly optimized <CODE>qsort()</CODE> routine. The new <CODE>qsort()</CODE> is resistant to inconsistent comparison functions, so Perl's [perlfunc:sort|sort()] will not provoke coredumps any more when given poorly written sort subroutines. (Some C library <CODE>qsort()</CODE>s that were being used before used to have this problem.) In our testing, the new <CODE>qsort()</CODE> required the minimal number of pair-wise compares on average, among all known <CODE>qsort()</CODE> implementations. See <CODE>perlfunc/sort</CODE>. <HR> <H2><A NAME="Reliable_signals">Reliable signals</A></H2> Perl's signal handling is susceptible to random crashes, because signals arrive asynchronously, and the Perl runtime is not reentrant at arbitrary times. However, one experimental implementation of reliable signals is available when threads are enabled. See <CODE>Thread::Signal</CODE>. Also see INSTALL for how to build a Perl capable of threads. <HR> <H2><A NAME="Reliable_stack_pointers">Reliable stack pointers</A></H2> The internals now reallocate the perl stack only at predictable times. In particular, magic calls never trigger reallocations of the stack, because all reentrancy of the runtime is handled using a ``stack of stacks''. This should improve reliability of cached stack pointers in the internals and in XSUBs. <HR> <H2><A NAME="More_generous_treatment_of_carri">More generous treatment of carriage returns</A></H2> Perl used to complain if it encountered literal carriage returns in scripts. Now they are mostly treated like whitespace within program text. Inside string literals and here documents, literal carriage returns are ignored if they occur paired with newlines, or get interpreted as newlines if they stand alone. This behavior means that literal carriage returns in files should be avoided. You can get the older, more compatible (but less generous) behavior by defining the preprocessor symbol <CODE>PERL_STRICT_CR</CODE> when building perl. Of course, all this has nothing whatever to do with how escapes like <CODE>\r</CODE> are handled within strings. Note that this doesn't somehow magically allow you to keep all text files in DOS format. The generous treatment only applies to files that perl itself parses. If your C compiler doesn't allow carriage returns in files, you may still be unable to build modules that need a C compiler. <HR> <H2><A NAME="Memory_leaks">Memory leaks</A></H2> [perlfunc:substr|substr], [perlfunc:pos|pos] and [perlfunc:vec|vec] don't leak memory anymore when used in lvalue context. Many small leaks that impacted applications that embed multiple interpreters have been fixed. <HR> <H2><A NAME="Better_support_for_multiple_inte">Better support for multiple interpreters</A></H2> The build-time option <CODE>-DMULTIPLICITY</CODE> has had many of the details reworked. Some previously global variables that should have been per-interpreter now are. With care, this allows interpreters to call each other. See the <CODE>PerlInterp</CODE> extension on CPAN. <HR> <H2><A NAME="Behavior_of_local_on_array_and">Behavior of local() on array and hash elements is now well-defined</A></H2> See [perlman:perlsub]. <HR> <H2><A NAME="C_is_transparently_tied_to_t"><CODE>%!</CODE> is transparently tied to the the Errno manpage module</A></H2> See [perlman:perlvar|the perlvar manpage], and the Errno manpage. <HR> <H2><A NAME="Pseudo_hashes_are_supported">Pseudo-hashes are supported</A></H2> See [perlman:perlref|the perlref manpage]. <HR> <H2><A NAME="C_EXPR_foreach_EXPR_is_supporte"><CODE>EXPR foreach EXPR</CODE> is supported</A></H2> See [perlman:perlsyn|the perlsyn manpage]. <HR> <H2><A NAME="Keywords_can_be_globally_overrid">Keywords can be globally overridden</A></H2> See [perlman:perlsub|the perlsub manpage]. <HR> <H2><A NAME="C_E_is_meaningful_on_Win32"><CODE>$^E</CODE> is meaningful on Win32</A></H2> See [perlman:perlvar|the perlvar manpage]. <HR> <H2><A NAME="C_foreach_1_1000000_optimize"><CODE>foreach (1..1000000)</CODE> optimized</A></H2> <CODE>foreach (1..1000000)</CODE> is now optimized into a counting loop. It does not try to allocate a 1000000-size list anymore. <HR> <H2><A NAME="C_Foo_can_be_used_as_implicit"><CODE>Foo::</CODE> can be used as implicitly quoted package name</A></H2> Barewords caused unintuitive behavior when a subroutine with the same name as a package happened to be defined. Thus, <CODE>new Foo @args</CODE>, use the result of the call to <CODE>Foo()</CODE> instead of <CODE>Foo</CODE> being treated as a literal. The recommended way to write barewords in the indirect object slot is <CODE>new Foo:: @args</CODE>. Note that the method <CODE>new()</CODE> is called with a first argument of <CODE>Foo</CODE>, not <CODE>Foo::</CODE> when you do that. <HR> <H2><A NAME="C_exists_Foo_Bar_tests_ex"><CODE>exists $Foo::{Bar::}</CODE> tests existence of a package</A></H2> It was impossible to test for the existence of a package without actually creating it before. Now <CODE>exists $Foo::{Bar::}</CODE> can be used to test if the <CODE>Foo::Bar</CODE> namespace has been created. <HR> <H2><A NAME="Better_locale_support">Better locale support</A></H2> See [perlman:perllocale|the perllocale manpage]. <HR> <H2><A NAME="Experimental_support_for_64_bit_">Experimental support for 64-bit platforms</A></H2> Perl5 has always had 64-bit support on systems with 64-bit longs. Starting with 5.005, the beginnings of experimental support for systems with 32-bit long and 64-bit 'long long' integers has been added. If you add -DUSE_LONG_LONG to your ccflags in config.sh (or manually define it in perl.h) then perl will be built with 'long long' support. There will be many compiler warnings, and the resultant perl may not work on all systems. There are many other issues related to third-party extensions and libraries. This option exists to allow people to work on those issues. <HR> <H2><A NAME="prototype_returns_useful_resul">prototype() returns useful results on builtins</A></H2> See [perlfunc:prototype|prototype]. <HR> <H2><A NAME="Extended_support_for_exception_h">Extended support for exception handling</A></H2> [perlfunc:die|die()] now accepts a reference value, and <CODE>$@</CODE> gets set to that value in exception traps. This makes it possible to propagate exception objects. This is an undocumented experimental feature. <HR> <H2><A NAME="Re_blessing_in_DESTROY_support">Re-blessing in DESTROY() supported for chaining DESTROY() methods</A></H2> See [perlman:perlobj]. <HR> <H2><A NAME="All_C_printf_format_conversions">All [perlfunc:printf|printf] format conversions are handled internally</A></H2> See [perlfunc:printf|printf]. <HR> <H2><A NAME="New_C_INIT_keyword">New <CODE>INIT</CODE> keyword</A></H2> <CODE>INIT</CODE> subs are like <CODE>BEGIN</CODE> and <CODE>END</CODE>, but they get run just before the perl runtime begins execution. e.g., the Perl Compiler makes use of <CODE>INIT</CODE> blocks to initialize and resolve pointers to XSUBs. <HR> <H2><A NAME="New_C_lock_keyword">New <CODE>lock</CODE> keyword</A></H2> The <CODE>lock</CODE> keyword is the fundamental synchronization primitive in threaded perl. When threads are not enabled, it is currently a noop. To minimize impact on source compatibility this keyword is ``weak'', i.e., any user-defined subroutine of the same name overrides it, unless a <CODE>use Thread</CODE> has been seen. <HR> <H2><A NAME="New_C_qr_operator">New [perlman:perlop] operator</A></H2> The [perlman:perlop] operator, which is syntactically similar to the other quote-like operators, is used to create precompiled regular expressions. This compiled form can now be explicitly passed around in variables, and interpolated in other regular expressions. See [perlman:perlop|the perlop manpage]. <HR> <H2><A NAME="C_our_is_now_a_reserved_word"><CODE>our</CODE> is now a reserved word</A></H2> Calling a subroutine with the name <CODE>our</CODE> will now provoke a warning when using the <CODE>-w</CODE> switch. <HR> <H2><A NAME="Tied_arrays_are_now_fully_suppor">Tied arrays are now fully supported</A></H2> See Array. <HR> <H2><A NAME="Tied_handles_support_is_better">Tied handles support is better</A></H2> Several missing hooks have been added. There is also a new base class for TIEARRAY implementations. See Array. <HR> <H2><A NAME="4th_argument_to_substr">4th argument to substr</A></H2> <CODE>substr()</CODE> can now both return and replace in one operation. The optional 4th argument is the replacement string. See [perlfunc:substr|substr]. <HR> <H2><A NAME="Negative_LENGTH_argument_to_spli">Negative LENGTH argument to splice</A></H2> <CODE>splice()</CODE> with a negative LENGTH argument now work similar to what the LENGTH did for <CODE>substr().</CODE> Previously a negative LENGTH was treated as 0. See [perlfunc:splice|splice]. <HR> <H2><A NAME="Magic_lvalues_are_now_more_magic">Magic lvalues are now more magical</A></H2> When you say something like <CODE>substr($x, 5) = "hi"</CODE>, the scalar returned by <CODE>substr()</CODE> is special, in that any modifications to it affect $x. (This is called a 'magic lvalue' because an 'lvalue' is something on the left side of an assignment.) Normally, this is exactly what you would expect to happen, but Perl uses the same magic if you use <CODE>substr(),</CODE> <CODE>pos(),</CODE> or <CODE>vec()</CODE> in a context where they might be modified, like taking a reference with <CODE>\</CODE> or as an argument to a sub that modifies <CODE>@_</CODE>. In previous versions, this 'magic' only went one way, but now changes to the scalar the magic refers to ($x in the above example) affect the magic lvalue too. For instance, this code now acts differently: <PRE> $x = "hello"; sub printit { $x = "g'bye"; print $_[0], "\n"; } printit(substr($x, 0, 5)); </PRE> In previous versions, this would print ``hello'', but it now prints ``g'bye''. <HR> <H2><A NAME="E_lt_E_gt_now_reads_in_records">Å¼ìô¾Å¼çô¾ now reads in records</A></H2> If <CODE>$/</CODE> is a referenence to an integer, or a scalar that holds an integer, <> will read in records instead of lines. For more info, see [perlman:perlvar]. <HR> <H1><A NAME="Supported_Platforms">Supported Platforms</A></H1> Configure has many incremental improvements. Site-wide policy for building perl can now be made persistent, via Policy.sh. Configure also records the command-line arguments used in config.sh. <HR> <H2><A NAME="New_Platforms">New Platforms</A></H2> BeOS is now supported. See README.beos. DOS is now supported under the DJGPP tools. See the README.dos manpage. MPE/iX is now supported. See README.mpeix. MVS (OS390) is now supported. See README.os390. <HR> <H2><A NAME="Changes_in_existing_support">Changes in existing support</A></H2> Win32 support has been vastly enhanced. Support for Perl Object, a C++ encapsulation of Perl. GCC and EGCS are now supported on Win32. See README.win32, aka perlwin32. VMS configuration system has been rewritten. See README.vms. The hints files for most Unix platforms have seen incremental improvements. <HR> <H1><A NAME="Modules_and_Pragmata">Modules and Pragmata</A></H1> <HR> <H2><A NAME="New_Modules">New Modules</A></H2> <DL> <DT><A NAME="item_B">B</A> <DD> Perl compiler and tools. See the B manpage. <DT><A NAME="item_Data">Data::Dumper</A> <DD> A module to pretty print Perl data. See Dumper. <DT><A NAME="item_Errno">Errno</A> <DD> A module to look up errors more conveniently. See the Errno manpage. <DT><A NAME="item_File">File::Spec</A> <DD> A portable API for file operations. <DT><A NAME="item_ExtUtils">ExtUtils::Installed</A> <DD> Query and manage installed modules. <DT><A NAME="item_ExtUtils">ExtUtils::Packlist</A> <DD> Manipulate .packlist files. <DT><A NAME="item_Fatal">Fatal</A> <DD> Make functions/builtins succeed or die. <DT><A NAME="item_IPC">IPC::SysV</A> <DD> Constants and other support infrastructure for System V IPC operations in perl. <DT><A NAME="item_Test">Test</A> <DD> A framework for writing testsuites. <DT><A NAME="item_Tie">Tie::Array</A> <DD> Base class for tied arrays. <DT><A NAME="item_Tie">Tie::Handle</A> <DD> Base class for tied handles. <DT><A NAME="item_Thread">Thread</A> <DD> Perl thread creation, manipulation, and support. <DT><A NAME="item_attrs">attrs</A> <DD> Set subroutine attributes. <DT><A NAME="item_fields">fields</A> <DD> Compile-time class fields. <DT><A NAME="item_re">re</A> <DD> Various pragmata to control behavior of regular expressions. </DL> <HR> <H2><A NAME="Changes_in_existing_modules">Changes in existing modules</A></H2> <DL> <DT><A NAME="item_CGI">CGI</A> <DD> CGI has been updated to version 2.42. <DT><A NAME="item_POSIX">POSIX</A> <DD> POSIX now has its own platform-specific hints files. <DT><A NAME="item_DB_File">DB_File</A> <DD> DB_File supports version 2.x of Berkeley DB. See <CODE>ext/DB_File/Changes</CODE>. <DT><A NAME="item_MakeMaker">MakeMaker</A> <DD> MakeMaker now supports writing empty makefiles, provides a way to specify that site <CODE>umask()</CODE> policy should be honored. There is also better support for manipulation of .packlist files, and getting information about installed modules. Extensions that have both architecture-dependent and architecture-independent files are now always installed completely in the architecture-dependent locations. Previously, the shareable parts were shared both across architectures and across perl versions and were therefore liable to be overwritten with newer versions that might have subtle incompatibilities. <DT><A NAME="item_CPAN">CPAN</A> <DD> See <perlmodinstall> and the CPAN manpage. <DT><A NAME="item_Cwd">Cwd</A> <DD> Cwd::cwd is faster on most platforms. <DT><A NAME="item_Benchmark">Benchmark</A> <DD> Keeps better time. </DL> <HR> <H1><A NAME="Utility_Changes">Utility Changes</A></H1> <CODE>h2ph</CODE> and related utilities have been vastly overhauled. <CODE>perlcc</CODE>, a new experimental front end for the compiler is available. The crude GNU <CODE>configure</CODE> emulator is now called <CODE>configure.gnu</CODE> to avoid trampling on <CODE>Configure</CODE> under case-insensitive filesystems. <CODE>perldoc</CODE> used to be rather slow. The slower features are now optional. In particular, case-insensitive searches need the <CODE>-i</CODE> switch, and recursive searches need <CODE>-r</CODE>. You can set these switches in the <CODE>PERLDOC</CODE> environment variable to get the old behavior. <HR> <H1><A NAME="Documentation_Changes">Documentation Changes</A></H1> Config.pm now has a glossary of variables. Porting/patching.pod has detailed instructions on how to create and submit patches for perl. [perlman:perlport|the perlport manpage] specifies guidelines on how to write portably. [perlman:perlmodinstall|the perlmodinstall manpage] describes how to fetch and install modules from <CODE>CPAN</CODE> sites. Some more Perl traps are documented now. See [perlman:perltrap|the perltrap manpage]. <HR> <H1><A NAME="New_Diagnostics">New Diagnostics</A></H1> <DL> <DT><A NAME="item_Ambiguous">Ambiguous call resolved as CORE::%s(), qualify as such or use &</A> <DD> (W) A subroutine you have declared has the same name as a Perl keyword, and you have used the name without qualification for calling one or the other. Perl decided to call the builtin because the subroutine is not imported. To force interpretation as a subroutine call, either put an ampersand before the subroutine name, or qualify the name with its package. Alternatively, you can import the subroutine (or pretend that it's imported with the <CODE>use subs</CODE> pragma). To silently interpret it as the Perl operator, use the <CODE>CORE::</CODE> prefix on the operator (e.g. <CODE>CORE::log($x)</CODE>) or by declaring the subroutine to be an object method (see the attrs manpage). <DT><A NAME="item_Bad">Bad index while coercing array into hash</A> <DD> (F) The index looked up in the hash found as the 0'th element of a pseudo-hash is not legal. Index values must be at 1 or greater. See [perlman:perlref|the perlref manpage]. <DT><A NAME="item_Bareword">Bareword "%s" refers to nonexistent package</A> <DD> (W) You used a qualified bareword of the form <CODE>Foo::</CODE>, but the compiler saw no other uses of that namespace before that point. Perhaps you need to predeclare a package? <DT><A NAME="item_Can">Can't call method "%s" on an undefined value</A> <DD> (F) You used the syntax of a method call, but the slot filled by the object reference or package name contains an undefined value. Something like this will reproduce the error: <PRE> $BADREF = 42; process $BADREF 1,2,3; $BADREF->process(1,2,3); </PRE> <DT>Can't coerce array into hash <DD> (F) You used an array where a hash was expected, but the array has no information on how to map from keys to array indices. You can do that only with arrays that have a hash reference at index 0. <DT>Can't goto subroutine from an eval-string <DD> (F) The ``goto subroutine'' call can't be used to jump out of an eval ``string''. (You can use it to jump out of an eval {BLOCK}, but you probably don't want to.) <DT>Can't localize pseudo-hash element <DD> (F) You said something like <CODE>local $ar->{'key'}</CODE>, where <CODE>$ar</CODE> is a reference to a pseudo-hash. That hasn't been implemented yet, but you can get a similar effect by localizing the corresponding array element directly -- <CODE>local $ar->[$ar->[0]{'key'}]</CODE>. <DT>Can't use %%! because Errno.pm is not available <DD> (F) The first time the %! hash is used, perl automatically loads the Errno.pm module. The Errno module is expected to tie the %! hash to provide symbolic names for <CODE>$!</CODE> errno values. <DT><A NAME="item_Cannot">Cannot find an opnumber for "%s"</A> <DD> (F) A string of a form <CODE>CORE::word</CODE> was given to <CODE>prototype(),</CODE> but there is no builtin with the name <CODE>word</CODE>. <DT><A NAME="item_Character">Character class syntax [. .] is reserved for future extensions</A> <DD> (W) Within regular expression character classes ([]) the syntax beginning with ``[.'' and ending with ``.]'' is reserved for future extensions. If you need to represent those character sequences inside a regular expression character class, just quote the square brackets with the backslash: ``\[.'' and ``.\]''. <DT>Character class syntax [: :] is reserved for future extensions <DD> (W) Within regular expression character classes ([]) the syntax beginning with ``[:'' and ending with ``:]'' is reserved for future extensions. If you need to represent those character sequences inside a regular expression character class, just quote the square brackets with the backslash: ``\[:'' and ``:\]''. <DT>Character class syntax [= =] is reserved for future extensions <DD> (W) Within regular expression character classes ([]) the syntax beginning with ``[='' and ending with ``=]'' is reserved for future extensions. If you need to represent those character sequences inside a regular expression character class, just quote the square brackets with the backslash: ``\[='' and ``=\]''. <DT><A NAME="item__s_">%s: Eval-group in insecure regular expression</A> <DD> (F) Perl detected tainted data when trying to compile a regular expression that contains the <CODE>(?{ ... })</CODE> zero-width assertion, which is unsafe. See [perlman:perlre], and [perlman:perlsec|the perlsec manpage]. <DT>%s: Eval-group not allowed, use re 'eval' <DD> (F) A regular expression contained the <CODE>(?{ ... })</CODE> zero-width assertion, but that construct is only allowed when the <CODE>use re 'eval'</CODE> pragma is in effect. See [perlman:perlre]. <DT>%s: Eval-group not allowed at run time <DD> (F) Perl tried to compile a regular expression containing the <CODE>(?{ ... })</CODE> zero-width assertion at run time, as it would when the pattern contains interpolated values. Since that is a security risk, it is not allowed. If you insist, you may still do this by explicitly building the pattern from an interpolated string at run time and using that in an <CODE>eval().</CODE> See [perlman:perlre]. <DT><A NAME="item_Explicit">Explicit blessing to '' (assuming package main)</A> <DD> (W) You are blessing a reference to a zero length string. This has the effect of blessing the reference into the package main. This is usually not what you want. Consider providing a default target package, e.g. <CODE>bless($ref,</CODE> <CODE>$p</CODE> or 'MyPackage'); <DT><A NAME="item_Illegal">Illegal hex digit ignored</A> <DD> (W) You may have tried to use a character other than 0 - 9 or A - F in a hexadecimal number. Interpretation of the hexadecimal number stopped before the illegal character. <DT><A NAME="item_No">No such array field</A> <DD> (F) You tried to access an array as a hash, but the field name used is not defined. The hash at index 0 should map all valid field names to array indices for that to work. <DT>No such field "%s" in variable %s of type %s <DD> (F) You tried to access a field of a typed variable where the type does not know about the field name. The field names are looked up in the <CODE>%FIELDS</CODE> hash in the type package at compile time. The <CODE>%FIELDS</CODE> hash is usually set up with the 'fields' pragma. <DT><A NAME="item_Out">Out of memory during ridiculously large request</A> <DD> (F) You can't allocate more than 2^31+``small amount'' bytes. This error is most likely to be caused by a typo in the Perl program. e.g., <CODE>$arr[time]</CODE> instead of <CODE>$arr[$time]</CODE>. <DT><A NAME="item_Range">Range iterator outside integer range</A> <DD> (F) One (or both) of the numeric arguments to the range operator ``..'' are outside the range which can be represented by integers internally. One possible workaround is to force Perl to use magical string increment by prepending ``0'' to your numbers. <DT><A NAME="item_Recursive">Recursive inheritance detected while looking for method '%s' in package '%s'</A> <DD> (F) More than 100 levels of inheritance were encountered while invoking a method. Probably indicates an unintended loop in your inheritance hierarchy. <DT><A NAME="item_Reference">Reference found where even-sized list expected</A> <DD> (W) You gave a single reference where Perl was expecting a list with an even number of elements (for assignment to a hash). This usually means that you used the anon hash constructor when you meant to use parens. In any case, a hash requires key/value pairs. <PRE> %hash = { one => 1, two => 2, }; # WRONG %hash = [ qw/ an anon array / ]; # WRONG %hash = ( one => 1, two => 2, ); # right %hash = qw( one 1 two 2 ); # also fine </PRE> <DT><A NAME="item_Undefined">Undefined value assigned to typeglob</A> <DD> (W) An undefined value was assigned to a typeglob, a la <CODE>*foo = undef</CODE>. This does nothing. It's possible that you really mean <CODE>undef *foo</CODE>. <DT><A NAME="item_Use">Use of reserved word "%s" is deprecated</A> <DD> (D) The indicated bareword is a reserved word. Future versions of perl may use it as a keyword, so you're better off either explicitly quoting the word in a manner appropriate for its context of use, or using a different name altogether. The warning can be suppressed for subroutine names by either adding a <CODE>&</CODE> prefix, or using a package qualifier, e.g. <CODE>&our()</CODE>, or <CODE>Foo::our()</CODE>. <DT><A NAME="item_perl">perl: warning: Setting locale failed.</A> <DD> (S) The whole warning message will look something like: <PRE> perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = "En_US", LANG = (unset) are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). </PRE> Exactly what were the failed locale settings varies. In the above the settings were that the LC_ALL was ``En_US'' and the LANG had no value. This error means that Perl detected that you and/or your system administrator have set up the so-called variable system but Perl could not use those settings. This was not dead serious, fortunately: there is a ``default locale'' called ``C'' that Perl can and will use, the script will be run. Before you really fix the problem, however, you will get the same error message each time you run Perl. How to really fix the problem can be found in [perlman:perllocale|the perllocale manpage] section LOCALE PROBLEMS. </DL> <HR> <H1><A NAME="Obsolete_Diagnostics">Obsolete Diagnostics</A></H1> <DL> <DT>Can't mktemp() <DD> (F) The <CODE>mktemp()</CODE> routine failed for some reason while trying to process a -e switch. Maybe your /tmp partition is full, or clobbered. <DT>Can't write to temp file for -e: %s <DD> (F) The write routine failed for some reason while trying to process a -e switch. Maybe your /tmp partition is full, or clobbered. <DT>Cannot open temporary file <DD> (F) The create routine failed for some reason while trying to process a -e switch. Maybe your /tmp partition is full, or clobbered. </DL> <HR> <H1><A NAME="BUGS">BUGS</A></H1> If you find what you think is a bug, you might check the headers of recently posted articles in the comp.lang.perl.misc newsgroup. There may also be information at <A HREF="http://www.perl.com/perl/,">http://www.perl.com/perl/,</A> the Perl Home Page. If you believe you have an unreported bug, please run the perlbug program included with your release. Make sure you trim your bug down to a tiny but sufficient test case. Your bug report, along with the output of <CODE>perl -V</CODE>, will be sent off to <perlbug@perl.com> to be analysed by the Perl porting team. <HR> <H1><A NAME="SEE_ALSO">SEE ALSO</A></H1> The Changes file for exhaustive details on what changed. The INSTALL file for how to build Perl. The README file for general stuff. The Artistic and Copying files for copyright information. <HR> <H1><A NAME="HISTORY">HISTORY</A></H1> Written by Gurusamy Sarathy <gsar@umich.edu>, with many contributions from The Perl Porters. Send omissions or corrections to <perlbug@perl.com>. <HR> Return to the [Library]