X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperl5110delta.pod;h=7c668961ac59d613ccf47d814f294552a7ecb618;hb=ad1d1c50b82921d113440583db34ebc37c3bab8b;hp=82d11e4130c444e6d4ad809174be0093006439ea;hpb=f71d6157c7933c0d3df645f0411d97d7e2b66b2f;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perl5110delta.pod b/pod/perl5110delta.pod index 82d11e4..7c66896 100644 --- a/pod/perl5110delta.pod +++ b/pod/perl5110delta.pod @@ -1,14 +1,17 @@ =head1 NAME -perldelta - what is new for perl v5.11.0 +perl5110delta - what is new for perl v5.11.0 =head1 DESCRIPTION -This document describes differences between the 5.10.0 and the 5.11.0 -development releases. +This document describes differences between the 5.10.0 release and +the 5.11.0 development release. =head1 Incompatible Changes +=head2 In @INC, move ARCHLIB and PRIVLIB after the current version's site_perl and vendor_perl. + + =head2 Switch statement changes The handling of complex expressions by the C/C switch @@ -31,7 +34,9 @@ However, contrary to 5.10.0, evaluating the flip-flop operators in boolean context ensures it can now be useful in a C, notably for implementing bistable conditions, like in: - when (/^=begin/ .. /^=end/) { ... } + when (/^=begin/ .. /^=end/) { + # do something + } =item defined-or operator @@ -52,7 +57,7 @@ of the switch statements where smart matching is implicitly used. The smart match operator C<~~> is no longer commutative. The behaviour of a smart match now depends primarily on the type of its right hand -argument. Moreover, its semantics has been adjusted for greater +argument. Moreover, its semantics have been adjusted for greater consistency or usefulness in several cases. While the general backwards compatibility is maintained, several changes must be noted: @@ -126,8 +131,92 @@ would just ignore any keyword passed to them as a label name. Since such labels cannot be defined anymore, this kind of error will be avoided. +=head2 Other incompatible changes + +=over 4 + +=item * + +The semantics of C have changed slightly. +See L<"Modules and Pragmata"> for more information. + +=item * + +It is now a run-time error to use the smart match operator C<~~> +with an object that has no overload defined for it. (This way +C<~~> will not break encapsulation by matching against the +object's internal representation as a reference.) + +=item * + +The version control system used for the development of the perl +interpreter has been switched from Perforce to git. This is mainly an +internal issue that only affects people actively working on the perl core; +but it may have minor external visibility, for example in some of details +of the output of C. See L for more information. + +=item * + +The internal structure of the C directory in the perl source has +been reorganised. In general, a module C whose source was +stored under F is now located under F. Also, +some modules have been moved from F to F. This is purely a +source tarball change, and should make no difference to the compilation or +installation of perl, unless you have a very customised build process that +explicitly relies on this structure, or which hard-codes the C +F parameter. Specifically, this change does not by default +alter the location of any files in the final installation. + +=item * + +As part of the C 2.x to 3.x upgrade, the experimental +C module has been removed. +See L for more details. + +=item * + +As part of the C upgrade, the +C and C modules +have been removed from this distribution. + +=item * + +C no longer contains the C<%:patchlevel> hash. + +=item * + +This one is actually a change introduced in 5.10.0, but it was missed +from that release's perldelta, so it is mentioned here instead. + +A bugfix related to the handling of the C modifier and C resulted +in a change of behaviour between 5.8.x and 5.10.0: + + # matches in 5.8.x, doesn't match in 5.10.0 + $re = qr/^bar/; "foo\nbar" =~ /$re/m; + +=item * + +C now returns undef. + +=back + =head1 Core Enhancements +=head2 Unicode Character Database 5.1.0 + +The copy of the Unicode Character Database included in Perl 5.10.1 has +been updated to 5.1.0 from 5.0.0. See +L for the +notable changes. + +=head2 A proper interface for pluggable Method Resolution Orders + +As of Perl 5.10.1 there is a new interface for plugging and using method +resolution orders other than the default (linear depth first search). +The C3 method resolution order added in 5.10.0 has been re-implemented as +a plugin, without changing its Perl-space interface. See L for +more information. + =head2 The C pragma This pragma allows you to lexically disable or enable overloading @@ -168,14 +257,70 @@ L needs to be able to schedule individual non-conflicting test scripts itself, and there is no standard interface to C utilities to interact with their job schedulers. +Note that currently some test scripts may fail when run in parallel (most +notably C). If necessary run just the failing scripts +again sequentially and see if the failures go away. + =head2 The C<...> operator A new operator, C<...>, nicknamed the Yada Yada operator, has been added. It is intended to mark placeholder code, that is not yet implemented. See L. (chromatic) +=head2 DTrace support + +Some support for DTrace has been added. See "DTrace support" in F. + +=head2 Support for C in CPAN module metadata + +Both C and C now support the C keyword +in the C metadata file included in most recent CPAN distributions. +This allows distribution authors to specify configuration prerequisites that +must be installed before running F or F. + +See the documentation for C or C for more +on how to specify C when creating a distribution for CPAN. + +=head2 The C function can now operate on arrays + +=head2 Perl's core time-related functions are now Y2038 compliand + +=head2 The variable C<$,> may now be tied + +=head2 // now behaves like || in when clauses + +=head2 You can now set C<-W> from the C environment varialbe + + + =head1 Modules and Pragmata +=head2 New Modules and Pragmata + +=over 4 + +=item C + +This is a new lexically-scoped alternative for the C module. +The bundled version is 2.06_01. Note that in this release, using a string +eval when C is in effect can cause the autodie behaviour to leak +into the surrounding scope. See L for more details. + +=item C + +This has been added to the core (version 2.020). + +=item C + +This pragma establishes an ISA relationship with base classes at compile +time. It provides the key feature of C without the feature creep. + +=item C + +This has been added to the core (version 1.39). + +=back + =head2 Pragmata Changes =over 4 @@ -184,90 +329,1957 @@ See L. (chromatic) See L pragma"> above. +=item C + +Upgraded from version 0.08 to 0.09. + +=item C + +Upgraded from version 1.02 to 1.03. + +=item C + +Upgraded from version 2.13 to 2.14. See L for a replacement. + +=item C + +Upgraded from version 0.22 to 0.23. + +=item C + +Upgraded from version 0.22 to 0.23. + +=item C + +Upgraded from version 0.22 to 0.23. + +=item C + +Upgraded from version 1.06 to 1.07. + +The Unicode F database file has been added. This has the +effect of adding some extra C<\N> character names that formerly wouldn't +have been recognised; for example, C<"\N{LATIN CAPITAL LETTER GHA}">. + +=item C + +Upgraded from version 1.13 to 1.17. + +=item C + +The meaning of the C<:5.10> and C<:5.10.X> feature bundles has +changed slightly. The last component, if any (i.e. C) is simply ignored. +This is predicated on the assumption that new features will not, in +general, be added to maintenance releases. So C<:5.10> and C<:5.10.X> +have identical effect. This is a change to the behaviour documented for +5.10.0. + +=item C + +Upgraded from version 2.13 to 2.14 (this was just a version bump; there +were no functional changes). + +=item C + +Upgraded from version 0.5565 to 0.62. + +=item C + +Upgraded from version 1.06 to 1.07. + +=item C + +Upgraded from version 1.06 to 1.07. + +=item C + +See L pragma"> above. + +=item C + +Upgraded from version 0.74 to 0.77. + =back -=head2 Selected Changes to Core Modules +=head2 Updated Modules =over 4 +=item C + +Upgraded from version 0.24 to 0.34. + +=item C + +Upgraded from version 1.38 to 1.52. + +=item C + +Upgraded from version 0.79 to 0.85. + +=item C + +Upgraded from version 5.63 to 5.68. + +=item C + +Upgraded from version 1.05 to 1.06. + +=item C + +Upgraded from version 1.17 to 1.22. + +=item C + +Upgraded from version 1.05 to 1.11. + +=item C + +Upgraded from version 0.83 to 0.89. + +=item C + +Upgraded from version 1.09 to 1.11. + +=item C + +Upgraded from version 1.01 to 1.02. + +=item C + +Upgraded from version 1.10 to 1.11. + +=item C + +Upgraded from version 1.08 to 1.11. + L now includes all the necessary code to function. Previously, it used to be a lightweight placeholder that loaded the actual code from C on demand. C is now a simple, empty module kept for backwards compatibility for programs that used to pre-load it. -=back -=head1 Utility Changes +=item C -=head1 Documentation +Upgraded from version 3.29 to 3.43. +(also includes the "default_value for popup_menu()" fix from 3.45). -=head1 Performance Enhancements +=item C -=head1 Installation and Configuration Improvements +Upgraded from version 2.008 to 2.020. -=head1 Selected Bug Fixes +=item C -=over 4 +Upgraded from version 1.9205 to 1.9402. C has a local fix to +stop it being too verbose on download failure. -=item C<-I> on shebang line now adds directories in front of @INC +=item C -as documented, and as does C<-I> when specified on the command-line. -(Renée Bäcker) +Upgraded from version 0.84 to 0.88. -=item C is now fatal when called on non-numeric process identifiers +=item C -Previously, an 'undef' process identifier would be interpreted as a request to -kill process "0", which would terminate the current process group on POSIX -systems. Since process identifiers are always integers, killing a non-numeric -process is now fatal. +Upgraded from version 0.06_02 to 0.36. -=item C<-C> on the shebang line is once more permitted +=item C -if it is also specified on the command line. C<-C> on the shebang line used -to be a silent no-op I it was not also on the command line, so perl -5.10.0 disallowed it, which broke some scripts. Now perl checks whether it -is also on the command line and only dies if it is not. +Upgraded from version 3.25_01 to 3.30. -=back +=item C -=head1 New or Changed Diagnostics +Upgraded from version 2.121_14 to 2.124. -=head1 Changed Internals +=item C -=head1 Known Problems +Upgraded from version 1.01 to 1.02. -=head2 Platform Specific Problems +=item C -=head1 Reporting Bugs +Upgraded from version 1.816_1 to 1.820. -If you find what you think is a bug, you might check the articles -recently posted to the comp.lang.perl.misc newsgroup and the perl -bug database at http://bugs.perl.org/ . There may also be -information at http://www.perl.org/ , the Perl Home Page. +=item C -If you believe you have an unreported bug, please run the B -program included with your release. Be sure to trim your bug down -to a tiny but sufficient test case. Your bug report, along with the -output of C, will be sent off to perlbug@perl.org to be -analysed by the Perl porting team. +Upgraded from version 3.13 to 3.19. -If the bug you are reporting has security implications, which make it -inappropriate to send to a publicly archived mailing list, then please send -it to perl5-security-report@perl.org. This points to a closed subscription -unarchived mailing list, which includes all the core committers, who be able -to help assess the impact of issues, figure out a resolution, and help -co-ordinate the release of patches to mitigate or fix the problem across all -platforms on which Perl is supported. Please only use this address for security -issues in the Perl core, not for modules independently distributed on CPAN. +=item C -=head1 SEE ALSO +Upgraded from version 2.36_01 to 2.39. -The F file for exhaustive details on what changed. +=item C -The F file for how to build Perl. +Upgraded from version 5.45 to 5.47. -The F file for general stuff. +=item C + +Upgraded from version 1.01 to 1.03. + +=item C + +Upgraded from version 1.12 to 1.13. + +=item C + +Upgraded from version 1.08 to 1.10. + +=item C + +Upgraded from version 2.23 to 2.35. + +=item C + +Upgraded from version 1.10 to 1.11. + +=item C + +Upgraded from version 5.62 to 5.63. + +=item C + +Upgraded from version 0.21 to 0.2602. + +=item C + +Upgraded from version 1.13 to 1.16. + +=item C + +Upgraded from 0.20 to 0.22. (Note that neither of these versions are +available on CPAN.) + +=item C + +Upgraded from version 1.27 to 1.28. + +=item C + +Upgraded from version 1.44 to 1.54. + +=item C + +Upgraded from version 6.42 to 6.55_02. + +Note that C and C +have been removed from this distribution. + +=item C + +Upgraded from version 1.51_01 to 1.56. + +=item C + +Upgraded from version 2.18_02 to 2.2002. + +=item C + +Upgraded from version 1.05 to 2.06_01. See also the new pragma C. + +=item C + +Upgraded from version 2.76 to 2.77. + +=item C + +Upgraded from version 1.1005 to 1.1006. + +=item C + +Upgraded from version 2.11 to 2.14. + +File::Copy now always return 0 (not "") on failure. + +=item C + +Upgraded from version 0.14 to 0.20. + +=item C + +Upgraded from version 1.12 to 1.14. + +=item C + +Upgraded from version 2.04 to 2.07_03. + +=item C + +Upgraded from version 3.2501 to 3.30. + +=item C + +Upgraded from version 1.00 to 1.01. + +Added -X overloading, -M, -C and -A. + +=item C + +Upgraded from version 0.18 to 0.22. + +=item C + +Upgraded from version 1.07 to 1.08. + +=item C + +Upgraded from version 2.01 to 2.02. + +=item C + +Upgraded from version 0.82 to 0.84. + +=item C + +Upgraded from version 1.07 to 1.08. + +=item C + +Upgraded from version 1.49 to 1.50. + +=item C + +Upgraded from version 1.08 to 1.09. + +=item C + +Upgraded from version 2.37 to 2.38. + +=item C + +Upgraded from version 1.03 to 1.04. This fixes a memory leak. + +=item C + +Upgraded from version 1.00 to 1.01. + +=item C + +Upgraded from version 1.23_01 to 1.25. + +This makes non-blocking mode work on Windows in C +[CPAN #43573]. + +=item C + +Upgraded from version 2.008 to 2.020. + +=item C + +Upgraded from version 1.06 to 1.07. + +=item C + +Upgraded from version 1.27 to 1.28. + +=item C + +Upgraded from version 1.30_01 to 1.31. + +=item C + +Upgraded from version 1.07 to 1.09. + +=item C + +Upgraded from version 0.40_1 to 0.46. + +=item C + +Upgraded from version 1.02 to 1.04. + +=item C + +Upgraded from version 1.05 to 2.01. + +=item C + +Upgraded from version 0.5565 to 0.62. + +=item C + +Upgraded from version 1.19 to 1.21. + +=item C + +Upgraded from version 1.12 to 1.13. + +=item C + +Upgraded from version 0.01 to 0.02. + +=item C + +Upgraded from version 1.59 to 1.60. + +=item C + +Upgraded from version 1.88 to 1.89. + +=item C + +Upgraded from version 0.16 to 0.19. + +=item C + +Upgraded from version 0.21 to 0.22. + +=item C + +Upgraded from version 1.37 to 1.56. + +=item C + +Upgraded from version 1.04 to 1.20. + +=item C + +Upgraded from version 1.01_02 to 1.01_03 (just a minor documentation +change). + +=item C + +Upgraded from version 0.2808_01 to 0.34_02. + +=item C + +Upgraded from version 2.13 to 2.18. This release no longer contains the +C<%Module::CoreList::patchlevel> hash. + +=item C + +Upgraded from version 0.12 to 0.16. + +=item C + +Upgraded from version 0.22 to 0.30. + +=item C + +Upgraded from version 0.01 to 0.02. + +=item C + +Upgraded from version 3.6 to 3.9. + +=item C + +Upgraded from version 1.07 to 1.08. + +=item C + +Upgraded from version 2.33 to 2.36. + +=item C + +Upgraded from version 0.60_01 to 0.64. + +=item C + +Upgraded from version 0.32 to 0.34. + +=item C + +Upgraded from version 1.03 to 1.04. + +=item C + +Upgraded from version 0.01 to 0.02. + +=item C + +Upgraded from version 1.04 to 1.06. + +=item C + +Upgraded from version 0.04 to 0.07. + +=item C + +Upgraded from version 2.16 to 2.22. + +=item C + +Upgraded from version 1.35 to 1.37. + +=item Pod::Perldoc + +Upgrade from version 3.14_02 to 3.15. + +=item C + +Upgraded from version 3.05 to 3.07. + +=item C + +Upgraded from version 3.08 to 3.13. + +=item C + +Upgraded from version 1.13 to 1.17. + +=item C + +Upgraded from 2.12 to 2.18. + +=item C + +Upgraded from version 1.19 to 1.21. + +=item C + +Upgraded from 1.01 to 1.02. + +=item C + +Upgraded from 1.11 to 1.17. + +=item C + +Upgraded from 1.80 to 1.82. + +=item C + +Upgraded from 2.18 to 2.20. + +=item C + +Upgraded from version 2.13 to 2.14. Please see L. + +=item C + +Upgraded from version 1.06 to 1.07. + +=item C + +Upgraded from version 0.22 to 0.27. + +=item C + +Upgraded from version 1.12 to 2.01. + +=item C + +Upgraded from version 1.03 to 1.04. + +=item C + +Upgraded from version 0.18 to 0.20. + +=item C + +Upgraded from version 2.64 to 3.17. + +Note that one side-effect of the 2.x to 3.x upgrade is that the +experimental C module (and its supporting +C, C, C and C modules) have been +removed. If you still need this, then they are available in the +(unmaintained) C distribution on CPAN. + +=item C + +Upgraded from version 0.72 to 0.92. + +=item C + +Upgraded from version 3.26 to 3.27. + +=item C + +Upgraded from version 2007.1117 to 2009.0305. + +=item C + +Upgraded from version 2006.1117 to 2009.0305. + +=item C + +Upgraded from version 2.00 to 2.11. + +=item C + +Upgraded from version 2.01 to 2.09. + +=item C + +Upgraded from version 1.67 to 1.73. + +=item C + +Upgraded from version 1.14 to 1.29. + +=item C + +Upgraded from version 1.37 to 1.38. + +=item C + +This has documentation changes, and has been assigned a version for the +first time: version 4.2. + +=item C + +Upgraded from version 1.9711 to 1.9719. + +=item C + +Upgraded from version 1.18 to 1.1901. + +=item C + +Upgraded from version 1.12 to 1.15. + +=item C + +Upgraded from version 1.02 to 1.03. + +=item C + +Upgraded from version 0.25 to 0.27. + +C now works on Unified CJK code points added to later versions +of Unicode. + +C has new fields returned to provide both a simpler interface +and previously missing information. The old fields are retained for +backwards compatibility. Information about Turkic-specific code points is +now returned. + +The documentation has been corrected and expanded. + +=item C + +Upgraded from version 1.04 to 1.05. + +UNIVERSAL->import() is now deprecated. + + +=item C + +Upgraded from version 0.34 to 0.39. + +=item C + +Upgraded from version 0.1001_01 to 0.1101. + +=item C + +Upgraded from version 0.08 to 0.10. + +=back + +=head1 Utility Changes + +=over 4 + +=item F + +Now looks in C too, which is a recent addition to gcc's +search path. + +=item F + +No longer incorrectly treats enum values like macros (Daniel Burr). + +Now handles C++ style constants (C) properly in enums. (A patch from +Rainer Weikusat was used; Daniel Burr also proposed a similar fix). + +=item F + +C subroutines now work under the debugger. + +The debugger now correctly handles proxy constant subroutines, and +subroutine stubs. + + +=item F + + Perlbug now uses %Module::CoreList::bug_tracker to print out upstream bug tracker URLs. + +Where the user names a module that their bug report is about, and we know the +URL for its upstream bug tracker, provide a message to the user explaining +that the core copies the CPAN version directly, and provide the URL for +reporting the bug directly to upstream. + +=item F + +Perl 5.10.1 added a new utility F, which is a variant of +F, but for sending non-bug-reports to the authors and maintainers +of Perl. Getting nothing but bug reports can become a bit demoralising: +we'll see if this changes things. + +=back + +=head1 New Documentation + +=over 4 + +=item L + +This contains instructions on how to build perl for the Haiku platform. + +=item L + +This describes the new interface for pluggable Method Resolution Orders. + +=item L + +This document, by Richard Foley, provides an introduction to the use of +performance and optimization techniques which can be used with particular +reference to perl programs. + +=item L + +This describes how to access the perl source using the I version +control system. + +=item L + +This describes the new F utility. + +=back + +=head1 Changes to Existing Documentation + +The various large C files (which listed every change made to perl +over the last 18 years) have been removed, and replaced by a small file, +also called C, which just explains how that same information may +be extracted from the git version control system. + +The file F has been deleted, as it mainly described +interacting with the old Perforce-based repository, which is now obsolete. +Information still relevant has been moved to L. + +L, L, L and L are now all +generated at build time, rather than being shipped as part of the release. + +=head2 Documented -X overloading. + +=head2 Documented that when() treats specially most of the filetest operators + +=head2 Documented that DESTROY is subject to AUTOLOAD, and the related optimisations. + +=head2 Documented when as a syntax modifier + +=head2 Eliminated "Old Perl threads tutorial", which describes 5005 threads. + +pod/perlthrtut.pod is the same material reworked for ithreads. + +=head2 Removed a link to the attrs pragma, which has now been removed. + +=head2 update PERL_MEM_LOG in perlhack.pod + +=head2 Correct previous documentation: v-strings are not deprecated + +With version objects, we need them to use MODULE VERSION syntax. This +patch removes the deprecation note. + + +=head1 Performance Enhancements + +=over 4 + +=item * + +A new internal cache means that C will often be faster. + +=item * + +Under C, the locale-relevant information is now cached on +read-only values, such as the list returned by C. This makes +operations such as C in the scope of C much +faster. + +=item * + +Empty C methods are no longer called. + +=item * + +Faster sv_utf8_upgrade() + +=item * + +Speed up keys() on empty hash + +=back + +=head1 Installation and Configuration Improvements + +=head2 F reorganisation + +The layout of directories in F has been revised. Specifically, all +extensions are now flat, and at the top level, with C in pathnames +replaced by C<->, so that F is now F, +etc. The names of the extensions as specified to F, and as +reported by C<%Config::Config> under the keys C, +C, C and C have not changed, and +still use C. Hence this change will not have any affect once perl is +installed. However, C, C and C have now +become extensions in their own right, so if you run F with +options to specify an exact list of extensions to build, you will need to +change it to account for this. + +For 5.10.2, it is planned that many dual-life modules will have been moved +from F to F; again this will have no effect on an installed +perl, but will matter if you invoke F with a pre-canned list of +extensions to build. + +=head2 Configuration improvements + +If C and C are the same, then they are only added to +C<@INC> once. + +C<$Config{usedevel}> and the C-level C are now defined if +perl is built with C<-Dusedevel>. + +F will enable use of C<-fstack-protector>, to provide protection +against stack-smashing attacks, if the compiler supports it. + +F will now determine the correct prototypes for re-entrant +functions, and for C, if you are using a C++ compiler rather +than a C compiler. + +On Unix, if you build from a tree containing a git repository, the +configuration process will note the commit hash you have checked out, for +display in the output of C and C. Unpushed local commits +are automatically added to the list of local patches displayed by +C. + +=head2 Compilation improvements + +As part of the flattening of F, all extensions on all platforms are +built by F. This replaces the Unix-specific +F, VMS-specific F and Win32-specific +F. + +=head2 Platform Specific Changes + +=over 4 + +=item AIX + +Removed F for AIX 5L and 6.1. Only flock() was used from F. + +Removed F for AIX 5L and 6.1. The F is delivered as an +optional package with the AIX Toolbox. Unfortunately the 64 bit version +is broken. + +Hints changes mean that AIX 4.2 should work again. + +=item Cygwin + +On Cygwin we now strip the last number from the DLL. This has been the +behaviour in the cygwin.com build for years. The hints files have been +updated. + +=item FreeBSD + +The hints files now identify the correct threading libraries on FreeBSD 7 +and later. + +=item Irix + +We now work around a bizarre preprocessor bug in the Irix 6.5 compiler: +C unfortunately goes into K&R mode, but C doesn't. + +=item Haiku + +Patches from the Haiku maintainers have been merged in. Perl should now +build on Haiku. + +=item MirOS BSD + +Perl should now build on MirOS BSD. + +=item NetBSD + +Hints now supports versions 5.*. + +=item Stratus VOS + +Various changes from Stratus have been merged in. + +=item Symbian + +There is now support for Symbian S60 3.2 SDK and S60 5.0 SDK. + +=item Win32 + +Improved message window handling means that C and C messages +will no longer be dropped under race conditions. + +=item VMS + +Reads from the in-memory temporary files of C used to fail +if C<$/> was set to a numeric reference (to indicate record-style reads). +This is now fixed. + +VMS now supports C. + +Many improvements and cleanups have been made to the VMS file name handling +and conversion code. + +Enabling the C logical name now encodes a POSIX exit +status in a VMS condition value for better interaction with GNV's bash +shell and other utilities that depend on POSIX exit values. See +L for details. + +File::Copy now detects Unix compatibility mode on VMS. + +=back + +=head1 Selected Bug Fixes + +=over 4 + +=item + +=item C<-I> on shebang line now adds directories in front of @INC. +as documented, and as does C<-I> when specified on the command-line. +(Renée Bäcker) + +=item + +* C is now fatal when called on non-numeric process identifiers. +Previously, an 'undef' process identifier would be interpreted as a request to +kill process "0", which would terminate the current process group on POSIX +systems. Since process identifiers are always integers, killing a non-numeric +process is now fatal. + +=item * + +5.10.0 inadvertently disabled an optimisation, which caused a measurable +performance drop in list assignment, such as is often used to assign +function parameters from C<@_>. The optimisation has been re-instated, and +the performance regression fixed. + +=item * + +Fixed memory leak on C [RT #53038]. + +=item * + +Some potential coredumps in PerlIO fixed [RT #57322,54828]. + +=item * + +The debugger now works with lvalue subroutines. + +=item * + +The debugger's C command was broken on modules that defined constants +[RT #61222]. + +=item * + +C and string complement could return tainted values for untainted +arguments [RT #59998]. + +=item * + +The C<-i.suffix> command-line switch now recreates the file using +restricted permissions, before changing its mode to match the original +file. This eliminates a potential race condition [RT #60904]. + +=item * + +On some UNIX systems, the value in C<$?> would not have the top bit set +(C<$? & 128>) even if the child core dumped. + +=item * + +Under some circumstances, $^R could incorrectly become undefined +[RT #57042]. + +=item * + +(XS) In various hash functions, passing a pre-computed hash to when the +key is UTF-8 might result in an incorrect lookup. + +=item * + +(XS) Including F before F gave a compile-time error +[RT #57176]. + +=item * + +C<< $object->isa('Foo') >> would report false if the package C didn't +exist, even if the object's C<@ISA> contained C. + +=item * + +Various bugs in the new-to 5.10.0 mro code, triggered by manipulating +C<@ISA>, have been found and fixed. + +=item * + +Bitwise operations on references could crash the interpreter, e.g. +C<$x=\$y; $x |= "foo"> [RT #54956]. + +=item * + +Patterns including alternation might be sensitive to the internal UTF-8 +representation, e.g. + + my $byte = chr(192); + my $utf8 = chr(192); utf8::upgrade($utf8); + $utf8 =~ /$byte|X}/i; # failed in 5.10.0 + +=item * + +Within UTF8-encoded Perl source files (i.e. where C is in +effect), double-quoted literal strings could be corrupted where a C<\xNN>, +C<\0NNN> or C<\N{}> is followed by a literal character with ordinal value +greater than 255 [RT #59908]. + +=item * + +C failed to correctly deparse various constructs: +C [RT #62428], C [RT #62488], +C [RT #62484]. + +=item * + +Using C with no arguments could corrupt the perl stack. + +=item * + +The block form of C is now specifically trappable by C and +C. Previously it was erroneously treated like string C. + +=item * + +In 5.10.0, the two characters C<[~> were sometimes parsed as the smart +match operator (C<~~>) [RT #63854]. + +=item * + +In 5.10.0, the C<*> quantifier in patterns was sometimes treated as +C<{0,32767}> [RT #60034, #60464]. For example, this match would fail: + + ("ab" x 32768) =~ /^(ab)*$/ + +=item * + +C was limited to a 32 bit segment size on a 64 bit OS [RT #63924]. + +=item * + +Using C or C to exit a C block no longer produces a +spurious warning like the following: + + Exiting given via last at foo.pl line 123 + +=item * + +On Windows, C<'.\foo'> and C<'..\foo'> were treated differently than +C<'./foo'> and C<'../foo'> by C and C [RT #63492]. + +=item * + +Assigning a format to a glob could corrupt the format; e.g.: + + *bar=*foo{FORMAT}; # foo format now bad + +=item * + +Attempting to coerce a typeglob to a string or number could cause an +assertion failure. The correct error message is now generated, +C>. + +=item * + +Under C, C<-x> was using the wrong access mode. This +has been fixed [RT #49003]. + +=item * + +C on a tied scalar that returned a Unicode value would not be +correct the first time. This has been fixed. + +=item * + +Using an array C inside in array C could SEGV. This has been +fixed. [RT #51636] + +=item * + +A race condition inside C has been identified and +fixed. This used to cause various threading issues, including SEGVs. + +=item * + +In C, the use of C<()> groups in scalar context was internally +placing a list on the interpreter's stack, which manifested in various +ways, including SEGVs. This is now fixed [RT #50256]. + +=item * + +Magic was called twice in C, C<\&$x>, C and C. +These have all been fixed. + +=item * + +A 5.10.0 optimisation to clear the temporary stack within the implicit +loop of C has been reverted, as it turned out to be the cause of +obscure bugs in seemingly unrelated parts of the interpreter [commit +ef0d4e17921ee3de]. + +=item * + +The line numbers for warnings inside C are now correct. + +=item * + +The C<..> operator now works correctly with ranges whose ends are at or +close to the values of the smallest and largest integers. + +=item * + +C could lead to segmentation faults on some platforms. +This has been fixed [RT #54828]. + +=item * + +An off-by-one error meant that C was effectively being +executed as C. This has been fixed [RT #53746]. + +=item * + +Various leaks associated with named captures in regexes have been fixed +[RT #57024]. + +=item * + +A weak reference to a hash would leak. This was affecting C +[RT #56908]. + +=item * + +Using (?|) in a regex could cause a segfault [RT #59734]. + +=item * + +Use of a UTF-8 C within a closure could cause a segfault [RT #61520]. + +=item * + +Calling C or otherwise upgrading an SV could result in an +unaligned 64-bit access on the SPARC architecture [RT #60574]. + +=item * + +In the 5.10.0 release, C would incorrectly list +C<5.10.*> after C<5.8.*>; this affected the C<@INC> search order +[RT #67628]. + +=item * + +In 5.10.0, C returned a non-tainted value +[RT #52552]. + +=item * + +In 5.10.0, C and C could produce the fatal error +C when printing UTF-8 strings +[RT #62666]. + +=item * + +In the 5.10.0 release, a dynamically created C method might be +missed (method cache issue) [RT #60220,60232]. + +=item * + +In the 5.10.0 release, a combination of C and C could +cause a memory leak [RT #63110]. + +=item * + +C<-C> on the shebang (C<#!>) line is once more permitted if it is also +specified on the command line. C<-C> on the shebang line used to be a +silent no-op I it was not also on the command line, so perl 5.10.0 +disallowed it, which broke some scripts. Now perl checks whether it is +also on the command line and only dies if it is not [RT #67880]. + +=item * + +In 5.10.0, certain types of re-entrant regular expression could crash, +or cause the following assertion failure [RT #60508]: + + Assertion rx->sublen >= (s - rx->subbeg) + i failed + +=back + +=head1 New or Changed Diagnostics + +=over 4 + +=item C + +This new fatal error occurs when the C routine C was +passed a position that is not within the scalar's string buffer. This +could be caused by buggy XS code, and at this point recovery is not +possible. + +=item C + +This warning has been removed. In general, it only got produced in +conjunction with other warnings, and removing it allowed an ISA lookup +optimisation to be added. + +=item C + +This warning has been removed. + +=item C + +It is now possible to change the depth threshold for this warning from the +default of 100, by recompiling the F binary, setting the C +pre-processor macro C to the desired value. + +=back + +=head1 Changed Internals + +=over 4 + +=item * + +The J.R.R. Tolkien quotes at the head of C source file have been checked and +proper citations added, thanks to a patch from Tom Christiansen. + +=item * + +C now accepts a null first argument. In addition, a full audit +was made of the "not NULL" compiler annotations, and those for several +other internal functions were corrected. + +=item * + +New macros C, C, C, C +have been added to formalise the temporary saving of the C +variable. + +=item * + +The function C has been added to augment +C. + +=item * + +The function C has been added, equivalent to +C followed by C. + +=item * + +The function C has been added, equivalent to +C and then performing the action relevant to the flag. + +Two flag bits are currently supported. + +=over 4 + +=item C + +This will call C for you. (Note that this does not convert an +sequence of ISO 8859-1 characters to UTF-8). A wrapper, C +is available for this. + +=item C + +Call C on the new SV. + +=back + +There is also a wrapper that takes constant strings, C. + +=item * + +The function C has been added as a wrapper to +C. + +=item * + +The functions C and C are now +exported. + +=item * + +C has been exterminated from the core code, replaced by local STRLEN +temporaries, or C<*_nolen()> calls. Either approach is faster than C, +which is a pointer deference into the interpreter structure under ithreads, +and a global variable otherwise. + +=item * + +C used to leave freed memory accessible via SvMAGIC() on +the scalar. It now updates the linked list to remove each piece of magic +as it is freed. + +=item * + +Under ithreads, the regex in C is now reference counted. This +eliminates a lot of hackish workarounds to cope with it not being reference +counted. + +=item * + +C would sometimes incorrectly turn on C. +This has been fixed. + +=item * + +The I IV and NV flags are now not set if the string value has +trailing "garbage". This behaviour is consistent with not setting the +public IV or NV flags if the value is out of range for the type. + +=item * + +SV allocation tracing has been added to the diagnostics enabled by C<-Dm>. +The tracing can alternatively output via the C mechanism, if +that was enabled when the F binary was compiled. + +=item * + +Uses of C, C, C, C, C etc have been +replaced by C in the core code, and non-dual-life modules, as C +is clearer to those unfamiliar with the core code. + +=item * + +A macro C has been added, which on (non-pedantic) gcc will +not cast away C, returning a C. Macros C, +C etc build on this, casting to C etc without +casting away C. This allows proper compile-time auditing of +C correctness in the core, and helped picked up some errors (now +fixed). + +=item * + +Macros C and C have been added, for pushing SVs on the +stack and mortalizing them. + +=item * + +Use of the private structure C has changed slightly. Nothing +outside the core should be accessing this directly anyway. + +=item * + +A new tool, C has been added, that allows you +to view how a C preprocessor macro would be expanded when compiled. +This is handy when trying to decode the macro hell that is the perl +guts. + +=back + +=head1 New Tests + +Many modules updated from CPAN incorporate new tests. + +Several tests that have the potential to hang forever if they fail now +incorporate a "watchdog" functionality that will kill them after a timeout, +which helps ensure that C and C run to +completion automatically. (Jerry Hedden). + +Some core-specific tests have been added: + +=over 4 + +=item t/comp/retainedlines.t + +Check that the debugger can retain source lines from C. + +=item t/io/perlio_fail.t + +Check that bad layers fail. + +=item t/io/perlio_leaks.t + +Check that PerlIO layers are not leaking. + +=item t/io/perlio_open.t + +Check that certain special forms of open work. + +=item t/io/perlio.t + +General PerlIO tests. + +=item t/io/pvbm.t + +Check that there is no unexpected interaction between the internal types +C and C. + +=item t/mro/package_aliases.t + +Check that mro works properly in the presence of aliased packages. + +=item t/op/dbm.t + +Tests for C and C. + +=item t/op/index_thr.t + +Tests for the interaction of C and threads. + +=item t/op/pat_thr.t + +Tests for the interaction of esoteric patterns and threads. + +=item t/op/qr_gc.t + +Test that C doesn't leak. + +=item t/op/reg_email_thr.t + +Tests for the interaction of regex recursion and threads. + +=item t/op/regexp_qr_embed_thr.t + +Tests for the interaction of patterns with embedded C and threads. + +=item t/op/regexp_unicode_prop.t + +Tests for Unicode properties in regular expressions. + +=item t/op/regexp_unicode_prop_thr.t + +Tests for the interaction of Unicode properties and threads. + +=item t/op/reg_nc_tie.t + +Test the tied methods of C. + +=item t/op/reg_posixcc.t + +Check that POSIX character classes behave consistently. + +=item t/op/re.t + +Check that exportable C functions in F work. + +=item t/op/setpgrpstack.t + +Check that C works. + +=item t/op/substr_thr.t + +Tests for the interaction of C and threads. + +=item t/op/upgrade.t + +Check that upgrading and assigning scalars works. + +=item t/uni/lex_utf8.t + +Check that Unicode in the lexer works. + +=item t/uni/tie.t + +Check that Unicode and C work. + +=back + +=head1 Known Problems + +This is a list of some significant unfixed bugs, which are regressions +from either 5.10.0 or 5.8.x. + +=over 4 + +=item * + +C misbehaves in the presence of a lexical C<$_> +(typically introduced by C or implicitly by C). The variable +which gets set for each iteration is the package variable C<$_>, not the +lexical C<$_> [RT #67694]. + +A similar issue may occur in other modules that provide functions which +take a block as their first argument, like + + foo { ... $_ ...} list + +=item * + +The C pragma may generate a run-time error when a regex is +interpolated [RT #56444]: + + use charnames ':full'; + my $r1 = qr/\N{THAI CHARACTER SARA I}/; + "foo" =~ $r1; # okay + "foo" =~ /$r1+/; # runtime error + +A workaround is to generate the character outside of the regex: + + my $a = "\N{THAI CHARACTER SARA I}"; + my $r1 = qr/$a/; + +=item * + +Some regexes may run much more slowly when run in a child thread compared +with the thread the pattern was compiled into [RT #55600]. + + +=back + +=head1 Deprecations + +The following items are now deprecated. + +=over 4 + +=item * + +C is buggy and should be avoided. From perl 5.11.0 onwards, it is +intended that any use of the core version of this module will emit a +warning, and that the module will eventually be removed from the core +(probably in perl 5.14.0). See L for its +replacement. + +=item * + +C has been removed. It used to provide a mechanism to +emulate setuid permission bits on systems that don't support it properly. + +=item * + +Deprecate assignment to $[ + +=item * + +Remove attrs, which has been deprecated since 1999/10/02. + +=item * + +Deprecate use of the attribute :locked on subroutines. + +=item * + +Deprecate using "locked" with the attributes pragma. + +=item * + +Deprecate using "unique" with the attributes pragma. + +=item * + +warn if ++ or -- are unable to change the value because it's beyond the limit of representation + +This uses a new warnings category: "imprecision". + + +=item * + +Make lc/uc/lcfirst/ucfirst warn when passed undef. + +=item * + +Show constant in "Useless use of a constant in void context" + +=item * + +Make the new warning report undef constants as undef + +=item * + +Add a new warning, "Prototype after '%s'" + +=item * + +Tweak the "Illegal character in prototype" warning so it's more precise when reporting illegal characters after _ + +=item * + +Unintented interpolation of $\ in regex + +=item * + +Make overflow warnings in gmtime/localtime only occur when warnings are on + +=item * + +Improve mro merging error messages. + +They are now very similar to those produced by Algorithm::C3. + +=item * + +Amelioration of the error message "Unrecognized character %s in column %d" + +Changes the error message to "Unrecognized character %s; marked by <-- +HERE after %s<-- HERE near column %d". This should make it a little +simpler to spot and correct the suspicious character. + +=item * + +Explicitely point to $. when it causes an uninitialized warning for ranges in scalar context + +=back + +=head1 Acknowledgements + +Some of the work in this release was funded by a TPF grant. + +Nicholas Clark officially retired from maintenance pumpking duty at the +end of 2008; however in reality he has put much effort in since then to +help get 5.10.1 into a fit state to be released, including writing a +considerable chunk of this perldelta. + +Steffen Mueller and David Golden in particular helped getting CPAN modules +polished and synchronised with their in-core equivalents. + +Craig Berry was tireless in getting maint to run under VMS, no matter how +many times we broke it for him. + +The other core committers contributed most of the changes, and applied most +of the patches sent in by the hundreds of contributors listed in F. + +Much of the work of categorizing changes in this perldelta file was contributed +by the following porters using changelogger.bestpractical.com: + +Nicholas Clark, leon, shawn, alexm, rjbs, rafl, Pedro Melo, brunorc, +anonymous, ☄, Tom Hukins, anonymous, Jesse, dagolden, Moritz Onken, +Mark Fowler, chorny, anonymous, tmtm + + +Finally, thanks to Larry Wall, without whom none of this would be +necessary. + +=head1 Reporting Bugs + +If you find what you think is a bug, you might check the articles +recently posted to the comp.lang.perl.misc newsgroup and the perl +bug database at http://rt.perl.org/perlbug/ . There may also be +information at http://www.perl.org/ , the Perl Home Page. + +If you believe you have an unreported bug, please run the B +program included with your release. Be sure to trim your bug down +to a tiny but sufficient test case. Your bug report, along with the +output of C, will be sent off to perlbug@perl.org to be +analysed by the Perl porting team. + +If the bug you are reporting has security implications, which make it +inappropriate to send to a publicly archived mailing list, then please send +it to perl5-security-report@perl.org. This points to a closed subscription +unarchived mailing list, which includes all the core committers, who be able +to help assess the impact of issues, figure out a resolution, and help +co-ordinate the release of patches to mitigate or fix the problem across all +platforms on which Perl is supported. Please only use this address for +security issues in the Perl core, not for modules independently +distributed on CPAN. + +=head1 SEE ALSO + +The F file for an explanation of how to view exhaustive details +on what changed. + +The F file for how to build Perl. + +The F file for general stuff. + +The F and F files for copyright information. + +=cut + + +=head1 TODO + +The following changes are a filtered list of changes which weren't backported +to 5.10.1. They were run through changelogger.bestpractical.com and triaged +by a set of Perl 5 Porters. Changes to blead after 5945e41e have not yet +been triaged or integrated. + +The following changes need to be + +1) deleted if they don't merit inclusion + + OR + +2) lightly copyedited and integrated into the perldelta above. Unfortunately, many of our +commit messages are somewhat terse and require a bit more help to turn into something readable + + + + +=head1 API + +=head2 Move the reg_stringify logic to Perl_sv_2pv_flags + +=head2 mg_copy ought to take an I32 + +=head2 Perl_store_cop_label() isn't meant to be part of the public API. + +=head2 Perl_gv_fetchmethod{,_autoload,_flags} are actually never* called with a non-NULL stash. +So change the parameter to NN. + + +=head2 Promote Perl_setdefout() to the public API. + +=head2 Add get_cvs() as a shortcut for STR_WITH_LEN() and Perl_get_cvn_flags() + +=head2 In Perl_newCONSTSUB(), sv should not be NULL. + +=head2 GvUNIQUE* have been defined as 0 since 2005/06/30 - high time to remove them. + +=head2 invert and rename PERL_MEM_LOG_STDERR to PERL_MEM_LOG_NOIMPL + +Most users who want PERL_MEM_LOG want the default implementation, +give it to them. Users providing their own implementation can +obtain current behavior by adding -DPERL_MEM_LOG_NOIMPL. +Frankly, the average user probably wants _ENV by default too. + +=head2 simplify PERL_MEM_LOG + +This combines multiple environment variable reads into 1, +where it looks for values like "2mst" +-2 leading digits are atoi()d to get FD +-m memory logging please +-s sv logging also +-t timestamp those please. + +Combining these reduces overhead such that it seemed +worthwhile to drop all the ifdefs. TBD whether this works +in the environment that drove the original tradeoffs. + +If it isnt enough, Id be tempted by a global static ptr, +and on 1st use, is read, seen 0, a lock is taken, and getenvar +run to populate it, unlocked, proceed. This would remove +iterative overheads. + +=head2 Add a parameter "destructing" to Gv_AMupdate() + +This boolean parameter indicates if the function has been called +to update the overload magic table while looking up the DESTROY +method. In this case, it's probably best to avoid croaking if +those tables could not be updated (for example due to a method +that could not be loaded.) + +=head2 Modify the return value of Gv_AMupdate to indicate a compilation error + +This way we'll restore most of the performance on object desctruction +lost by the previous commit + + +=head2 local $SIG{FOO} = sub {...}; sets signal handler to SIG_DFL + +Re: [perl #60360] [PATCH] UPDATED: local $SIG{FOO} = sub {...}; sets signal handler to SIG_DFL +Message-ID: <20081112234504.GI2062@tytlal.topaz.cx> + +Updated patch to retain source compatibility. + +Plus using the correct PERL_ARGS_ASSERT_SAVE_HELEM_FLAGS +macro and running make regen. + +=head2 Respecting inc_version_list while processing PERL_VENDORLIB_STEM + +Respecting inc_version_list while processing PERL_VENDORLIB_STEM +From: "Mandalemula, Rajesh" + +=head2 Change PL_debug behaviour + + +String eval lines are now saved whenever +a subroutine is defined, even if the eval'd string has subsequent +syntax errors. This allows the debugger to single step into these +subroutines. + + +=head2 Tied filehandles now have an additional method EOF which provides the EOF type + +=head2 Perl is now smarter about adding a -I dir to the beginning or end of @INC + +=head2 On scope end, delete localized array elements that should not exist anymore, so that the array recovers its previous length. Honour EXISTS and DELETE for tied arrays. + +=head2 When a glob is deleted, mark its sub as ANON. + +=head2 Require a space or a newline after a "#line XXX" directive + +=head2 Forbid using "foreach" as an attribute + +(like all other control flow statements) + + +=head2 Unregister signal handlers before destroying my_perl + +If the signal handler runs after perl_destruct() has been called, it +will get an invalid (or NULL) my_perl when it asks for the +thread-specific interpreter struct. This patch resets the signal +handler for any signal previously handled by PL_csighandlerp to SIG_DFL +before calling perl_destruct(). + +=head2 Perl_magic_clearsig() needs to remove magic, else delete $SIG{INT} returns undef + +Perl_magic_clearsig() needs to remove magic, else delete $SIG{INT} returns undef +instead of the now-removed INT handler. + +=head2 [perl #66452] TMPDIR not honored when opening an anonymous temporary file + +[perl #66452] TMPDIR not honored when opening an anonymous temporary file + +=head2 The attached patch to perlio.c fixes the problem of errno getting set. + +While I am firmly in the school of "do not look at $! except immediately +after a failure", I also agree that spuriously setting it is messy. But +there is just no way of knowing where your errno might have been. + +The problem was that PerlIO_fast_gets() (and other nearby similar +capability-checking PerlIO routines) set the errno (and it was being +called a lot, from sv_gets()). I think setting the errno here was +a mistake: checking for "can has FOO" should not set external state, +such as the errno. The patch removes that errno trashing from all those +routines. + +=head2 Trim all trailing / from "." in @INC when filling %INC + +This fixes bug #66942 : as a / was left in the directory name, +$INC{"Foo.pm"} for a file loaded from the current directory +was given the incorrect value "/Foo.pm". + +=head2 Don't enqueue pending signals during global destruction + +Global destruction is not signal-safe. PL_psig_pend may already +be gone when the signal handler is called (with destruct_level > 0). +NULL it before freeing it to prevent a race condition. + +=head2 Eliminate struct regexp_allocated and xpvio_allocated. + +Calculate memory allocation using regexp and XPVIO, and the offset of the first +real structure member. This avoids tripping over alignment differences between +X* and x*_allocated, because x*_allocated doesn't have a double in it. + + +=head1 internals + +=head2 [perl #47047] Use of inherited AUTOLOAD for non-method is deprecated + +=head2 Remove the definitions of Null(), Nullch, Nullfp, Nullsv and PL_na when code is within the perl source tree + +=head2 Replace our assert-which-can-be-caught-by-eval with the real deal from the standard C library. + +=head2 Tweak Perl_sv_upgrade() so that references can upgrade to SVt_PV + +=head2 Eliminate prelen from struct regexp. + +=head2 Change Perl_av_iter_p() to return IV* rather than I32* (which means + +=head2 Reorder the external regexp flags to get RXf_PMf_STD_PMMOD into the + +lowest 4 bits (which saves a shift), and the "flags indicating special +patterns" into contiguous bits. This makes everything a little tidier, +and saves 88 bytes (woohoo!) of object file with -Os on x86 FreeBSD. + + +=head2 Re-implement the SvOOK() hack to store the offset as a BER encoded number in the part of the PVX that is being released. +(It will always +fit, as chopping off 1 byte gives just enough space for recording a +delta of up to 127). This allows SvOOK() to co-exist with SvIOK_on(), +which means all the calls to SvOOK_off() [with the possibility of a +call to sv_backoff()] in SvIOK_on() can be removed. This ought to make +a lot of straight line code a little bit simpler. +OOK()d scalars can now be SVt_PV, as the IVX isn't needed. + +=head2 Abolish wraplen from struct regexp. We're already storing it in SvCUR. + +=head2 Make Perl_pregcomp() use SvUTF8() of the pattern, rather than the flag bit in pmflags, to decide whether the pattern is UTF-8. + +=head2 Abolish RXf_UTF8. Store the UTF-8-ness of the pattern with SvUTF8(). + +=head2 In struct regexp move the member paren_names to the IV union. + +=head2 Make REGEXP a type distinct from SV. (Much like AV, CV, GV, HV). + +=head2 Allow sv_setsv_flags() to copy SVt_REGEXP much like it copies SVt_FORMAT - the just string buffer. + + +=head2 Correct a long-standing ithreads reference counting anonamly + +The reference count only needs "doubling" when the scalar is pushed onto +PL_regex_padav for the second time. + + +=head2 In PL_regexp_padav, store regexps via real references, rather than hiding them within IVs. + +We can do this now that they are real SV pointers. + +=head2 With regexps stored as real RVs, we can eliminate SvREPADTMP(). + +=head2 REGEXPs are now stored directly in PL_regex_padav, rather than indirectly via RVs. + +=head2 Remove code that protected pp_qr against REGEXPs going away during global destruction whilst they were stored via true references in PL_regex_padav. + +=head2 Remove PM_GETRE_SAFE and PM_SETRE_SAFE as nothing uses them. + +=head2 Note the U8 sized space created by removing -P, and check that it is now an illegal command line flag. + +=head2 Pack the recycled pad offsets into an SV at PL_regex_pad[0]. + +=head2 Re-order so that the !SvOK() case is last (which should be rare) + +=head2 Extend PUSHFORMAT() to take a second parameter to set retop, to save NULLing it and then reassigning. + +=head2 Split struct block_sub into struct block_sub and struct block_format. + +Split struct block_sub into struct block_sub and struct block_format. +(CXt_SUB and CXt_FORMAT were using some comon members, but some members +were only for one or the other.) + +=head2 Change the wantarray result from caller from IV to bool for the SCALAR/ARRAY case. + +This doesn't contradict the documentation, as there isn't any. Oops. + + +=head2 Give G_VOID, G_SCALAR and G_ARRAY the same numeric values as OPf_WANT_VOID, OPf_WANT_SCALAR and OPf_WANT_LIST. + + +=head2 Squeeze the context type down to 4 bits, and move the private flags to fit within the next 4 bits. + + +=head2 In struct block change blku_type from U8 to U16, and the "spare" U8 to U16, with the lockstep changes in struct subst. +Eliminate lval from +struct block_sub, and instead store it in the U16 in struct block. + + +=head2 In struct block_eval, eliminate old_in_eval and old_op_type by storing the data in blk_u16. + + +=head2 The layout for struct block_loop under ithreads can be simplified. + +Instead of wedging the pad offset into a void* iterdata, and always +storing PL_comppad even when it isn't used, instead do this: + +PAD *oldcomppad; /* Also used for the GV, if targoffset is 0 */ +/* This is also accesible via cx->blk_loop.my_op->op_targ */ +PADOFFSET targoffset; + +and store the GV pointer in oldcompad. Pointers to pointers seems +cleaner. This also allows us to eliminate the flag bit CXp_PADVAR. + + +=head2 In XS_PerlIO_get_layers() take advantage of the implementation of + +In XS_PerlIO_get_layers() take advantage of the implementation of +PerlIO_get_layers(), by co-opting the new SVs it creates, rather than +copying them. + + +=head2 Micro-optimise the order of the context types. [Because I can :-)] + +=head2 [patch] optimize OP_IS_(FILETEST|SOCKET) macros + +=head2 Eliminate ck_lengthconst. + +=head2 Chainsaw DEBUG_S out, as suggested by Vincent Pit. + +=head2 Unsupported private API functions are now declared "static" to prevent leakage to the public API + +=head2 Perl_cv_ckproto() is not part of the public API, and not used anywhere. It has been removed + +=head2 Remove all the 5005threads specific mutex macros, which are now vestigial. + +=head2 Do not honor TMPDIR for anonymous temporary files when tainting + +Use a default of /tmp on Unixes when TMPDIR is unset or empty, or +when creation of a temporary file in it fails + +=head2 Add a pluggable hook in op_free() -The F and F files for copyright information. -=cut