X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/9948897efc093634ae400ccfcea5e013a2ae63d3..cfc946ee43aa15c20d9dcca961126b7b48a53c60:/pod/perl5110delta.pod diff --git a/pod/perl5110delta.pod b/pod/perl5110delta.pod index e96a64d..67938e9 100644 --- a/pod/perl5110delta.pod +++ b/pod/perl5110delta.pod @@ -1,65 +1,2214 @@ +=encoding utf8 + =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 release and +the 5.11.0 development release. + +=head1 Incompatible Changes + +=head2 Unicode interpretation of \w, \d, \s, and the POSIX character classes redefined. + +Previous versions of Perl tried to map POSIX style character class definitions onto +Unicode property names so that patterns would "dwim" when matches were made against latin-1 or +unicode strings. This proved to be a mistake, breaking character class negation, causing +forward compatibility problems (as Unicode keeps updating their property definitions and adding +new characters), and other problems. + +Therefore we have now defined a new set of artificial "unicode" property names which will be +used to do unicode matching of patterns using POSIX style character classes and perl short-form +escape character classes like \w and \d. + +The key change here is that \d will no longer match every digit in the unicode standard +(there are thousands) nor will \w match every word character in the standard, instead they +will match precisely their POSIX or Perl definition. + +Those needing to match based on Unicode properties can continue to do so by using the \p{} syntax +to match whichever property they like, including the new artificial definitions. + +B This is a backwards incompatible no-warning change in behaviour. If you are upgrading +and you process large volumes of text look for POSIX and Perl style character classes and +change them to the relevent property name (by removing the word 'Posix' from the current name). + +The following table maps the POSIX character class names, the escapes and the old and new +Unicode property mappings: + + POSIX Esc Class New-Property ! Old-Property + ----------------------------------------------+------------- + alnum [0-9A-Za-z] IsPosixAlnum ! IsAlnum + alpha [A-Za-z] IsPosixAlpha ! IsAlpha + ascii [\000-\177] IsASCII = IsASCII + blank [\011 ] IsPosixBlank ! + cntrl [\0-\37\177] IsPosixCntrl ! IsCntrl + digit \d [0-9] IsPosixDigit ! IsDigit + graph [!-~] IsPosixGraph ! IsGraph + lower [a-z] IsPosixLower ! IsLower + print [ -~] IsPosixPrint ! IsPrint + punct [!-/:-@[-`{-~] IsPosixPunct ! IsPunct + space [\11-\15 ] IsPosixSpace ! IsSpace + \s [\11\12\14\15 ] IsPerlSpace ! IsSpacePerl + upper [A-Z] IsPosixUpper ! IsUpper + word \w [0-9A-Z_a-z] IsPerlWord ! IsWord + xdigit [0-9A-Fa-f] IsXDigit = IsXDigit + +If you wish to build perl with the old mapping you may do so by setting + + #define PERL_LEGACY_UNICODE_CHARCLASS_MAPPINGS 1 + +in regcomp.h, and then setting + + PERL_TEST_LEGACY_POSIX_CC + +to true your enviornment when testing. + + +=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 +statement has been enhanced. These enhancements are also available in +5.10.1 and subsequent 5.10 releases. There are two new cases where C now +interprets its argument as a boolean, instead of an expression to be used +in a smart match: + +=over 4 + +=item flip-flop operators + +The C<..> and C<...> flip-flop operators are now evaluated in boolean +context, following their usual semantics; see L. + +Note that, as in perl 5.10.0, C will not work to test +whether a given value is an integer between 1 and 10; you should use +C instead (note the array reference). + +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/) { + # do something + } + +=item defined-or operator + +A compound expression involving the defined-or operator, as in +C, will be treated as boolean if the first +expression is boolean. (This just extends the existing rule that applies +to the regular or operator, as in C.) + +=back + +The next section details more changes brought to the semantics to +the smart match operator, that naturally also modify the behaviour +of the switch statements where smart matching is implicitly used. +These changers were also made for the 5.10.1 release, and will remain in +subsequent 5.10 releases. + +=head2 Smart match changes + +=head3 Changes to type-based dispatch + +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 have been adjusted for greater +consistency or usefulness in several cases. While the general backwards +compatibility is maintained, several changes must be noted: + +=over 4 + +=item * + +Code references with an empty prototype are no longer treated specially. +They are passed an argument like the other code references (even if they +choose to ignore it). + +=item * + +C<%hash ~~ sub {}> and C<@array ~~ sub {}> now test that the subroutine +returns a true value for each key of the hash (or element of the +array), instead of passing the whole hash or array as a reference to +the subroutine. + +=item * + +Due to the commutativity breakage, code references are no longer +treated specially when appearing on the left of the C<~~> operator, +but like any vulgar scalar. + +=item * + +C is always false (since C can't be a key in a +hash). No implicit conversion to C<""> is done (as was the case in perl +5.10.0). + +=item * + +C<$scalar ~~ @array> now always distributes the smart match across the +elements of the array. It's true if one element in @array verifies +C<$scalar ~~ $element>. This is a generalization of the old behaviour +that tested whether the array contained the scalar. + +=back + +The full dispatch table for the smart match operator is given in +L. + +=head3 Smart match and overloading + +According to the rule of dispatch based on the rightmost argument type, +when an object overloading C<~~> appears on the right side of the +operator, the overload routine will always be called (with a 3rd argument +set to a true value, see L.) However, when the object will +appear on the left, the overload routine will be called only when the +rightmost argument is a simple scalar. This way distributivity of smart match +across arrays is not broken, as well as the other behaviours with complex +types (coderefs, hashes, regexes). Thus, writers of overloading routines +for smart match mostly need to worry only with comparing against a scalar, +and possibly with stringification overloading; the other common cases +will be automatically handled consistently. + +C<~~> will now refuse to work on objects that do not overload it (in order +to avoid relying on the object's underlying structure). (However, if the +object overloads the stringification or the numification operators, and +if overload fallback is active, it will be used instead, as usual.) + +=head2 Labels can't be keywords + +Labels used as targets for the C, C, C or C +statements cannot be keywords anymore. This restriction will prevent +potential confusion between the C and C syntaxes: +for example, a statement like C would jump to a label whose +name would be the return value of C, (usually 1), instead of a +label named C. Moreover, the other control flow statements +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, +nearly all dual-life 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. + +=item * + +Unsupported private C API functions are now declared "static" to prevent +leakage to Perl's public API + +=item * + +F no longer builds with UTF-8 support in the regexp engine to support the bootstrapping process + +This allows a build to complete with PERL_UNICODE set and a UTF-8 locale. +Without this there's a bootstrapping problem, as miniperl can't load the UTF-8 +components of the regexp engine, because they're not yet built. + +=item * + +F's @INC is now restricted to just -I..., the split of $ENV{PERL5LIB}, and "." + +=item * + +A space or a newline is now required after a C<"#line XXX"> directive. + +=item * + +Tied filehandles now have an additional method EOF which provides the EOF type + +=item * + +To better match all other flow control statements, C may no longer be used as an attribute. + +=back + +=head1 Core Enhancements + +=head2 Unicode Character Database 5.1.0 + +The copy of the Unicode Character Database included in Perl 5.11.0 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.11.0 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 +for some or all operations. (Yuval Kogman) + +=head2 C<\N> regex escape + +A new regex escape has been added, C<\N>. It will match any character that +is not a newline, independently from the presence or absence of the single +line match modifier C. (If C<\N> is followed by an opening brace and +by a letter, perl will still assume that a Unicode character name is +coming, so compatibility is preserved.) (Rafael Garcia-Suarez) + +=head2 Implicit strictures + +Using the C syntax with a version number greater or equal +to 5.11.0 will also lexically enable strictures just like C +would do (in addition to enabling features.) So, the following: + + use 5.11.0; + +will now imply: + + use strict; + use feature ':5.11'; + +=head2 Parallel tests + +The core distribution can now run its regression tests in parallel on +Unix-like platforms. Instead of running C, set C in +your environment to the number of tests to run in parallel, and run +C. On a Bourne-like shell, this can be done as + + TEST_JOBS=3 make test_harness # Run 3 tests in parallel + +An environment variable is used, rather than parallel make itself, because +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 F 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 variable + +=head2 Add support for Abstract namespace sockets + +Abstract namespace sockets are Linux-specific socket type that live in +AF_UNIX family, slightly abusing it to be able to use arbitrary +character arrays as addresses: They start with nul byte and are not +terminated by nul byte, but with the length passed to the socket() +system call. + + +=head2 C now allows you to lexically delete a hash entry. + +=head1 Modules and Pragmata + +=head2 Dual-lifed modules moved + +Dual-lifed modules maintained primarily in the Perl core now live in dist/. +Dual-lifed modules maintained primarily on CPAN now live in cpan/ + +=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 + +=item C + +See L pragma"> above. + +=item C + +Upgraded from version 0.08 to 0.09. + +=item C + +The C pragma has been removed. It had been marked as deprecated since +5.6.0. + +=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.19. Some code has been shifted from run time to +compile time, and the amount of MRO cache flushing has been minimised. + +=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 1.00 to 1.01. Performance for single inheritance is 40% +faster - see L below. + +C is now implemented as an XS extension. The documented interface has not +changed. Code relying on the implementation detail that some C +methods happened to be available at all times gets to "keep both pieces". + +=item C + +Upgraded from version 0.74 to 0.77. + +=back + +=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. + +=item C + +Upgraded from version 3.29 to 3.43. +(also includes the "default_value for popup_menu()" fix from 3.45). + +=item C + +Upgraded from version 2.008 to 2.020. + +=item C + +Upgraded from version 1.9205 to 1.9402. C has a local fix to +stop it being too verbose on download failure. + +=item C + +Upgraded from version 0.84 to 0.88. + +=item C + +Upgraded from version 0.06_02 to 0.36. + +=item C + +Upgraded from version 3.25_01 to 3.30. + +=item C + +Upgraded from version 2.121_14 to 2.124. + +=item C + +Upgraded from version 1.01 to 1.02. + +=item C + +Upgraded from version 1.816_1 to 1.820. + +=item C + +Upgraded from version 3.13 to 3.19. + +=item C + +Upgraded from version 2.36_01 to 2.39. + +=item C + +Upgraded from version 5.45 to 5.47. + +=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.16. + +File::Copy now always return 0 (not "") on failure. + +FIXME - describe C + +=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 C + +Upgraded from version 0.01 to 1.01. + +There are no code changes - the version bump is because C has +been released to CPAN as a stand-alone distribution, and will be removed from +the core distribution in 5.14. + +=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.84. + +As of 1.84, C can now handle abstract namespace sockets on Linux. +(see unix(7)). + +=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. + +C<< 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. + +=item Upgrade to Class::ISA 0.34 + +=item Upgrade to Attribute::Handlers 0.87 + +=item Upgrade to AutoLoader 5.70 + +=item Upgrade to IO::Zlib 1.10 + +=item Update parent to CPAN version 0.223 + +=item Update Log::Message::Simple to CPAN version 0.06 + +=item Updated Math::BigRat to CPAN version 0.24 + +=item Update Archive::Tar to CPAN version 1.54 + +=item Update IPC::Cmd to CPAN version 0.50 + +=item Updated CPANPLUS::Dist::Build to CPAN version 0.40 + +=item Updated Module::Loaded to CPAN version 0.06 + +=item Upgrade Term::ANSIColor to 2.02 + +=item Update Text::Balanced to 2.02 + +=item Update Module::Build to 0.35 + +=item constant has been upgraded to 1.19. + +=item upgrade CGI from 3.43 to 3.45 + +=item bump Safe version to 2.18 + +=item Upgrade to threads::shared 1.31 + +=item Update threads to 1.74 + +=item autodie 2.06_01 + +=item Synchronize with CPAN's Attribute::Handlers 0.86 + +=item Synchronize AutoLoader with CPAN's 5.69 + +=item ExtUtils::MakeMaker 6.55_02 + +=item Final release of version-0.77 for inclusion in 5.10.1 + +=item Upgrade to Encode 2.37 + +=item Upgrade to Class::ISA 0.36 (Fixes installation directories only) + +=item Upgrade to PathTools 3.30_02 (with only core reorganization fixes) + +=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 + +F now uses C<%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.11.0 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 F files (which listed every change made to perl +over the last 18 years) have been removed, and replaced by a small file, +also called F, 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 C treats specially most of the filetest operators + +=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 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. + +=head2 Added security contact information to L + +=head1 Performance Enhancements + +=over 4 + +=item * + +A new internal cache means that C will often be faster. + +=item * + +The implementation of C Method Resolution Order has been optimised - +linearisation for classes with single inheritance is 40% faster. Performance +for multiple inheritance is unchanged. + +=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 C + +=item * + +Speed up C 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. C has been split out from being part of C, and +C is now an extension in its own right. + +Nearly all dual-life modules have been moved from F to F, and will +now appear as known C. This will made no difference to the +structure of an installed perl, nor will the modules installed differ, +unless you run F with options to specify an exact list of +extensions to build. In this case, you will rapidly become aware that you +need to add to your list, because various modules needed to complete the +build, such as C, have now become extensions, and +without them the build will fail well before it attempts to run the +regression tests. + +=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 C 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 DomainOS + +Support for Apollo DomainOS was removed in Perl 5.11.0 + +=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 MiNT + +Support for Atari MiNT was removed in Perl 5.11.0. + +=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. + +C now detects Unix compatibility mode on VMS. + +=back + +=head1 Selected Bug Fixes + +=over 4 + +=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. + +=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>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, C<$^R> could incorrectly become undefined +[RT #57042]. + +=item * + +In the XS API, various hash functions, when passed a pre-computed hash where +the key is UTF-8, might result in an incorrect lookup. + +=item * + +XS code 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 * -=head1 DESCRIPTION +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]. -This document describes differences between the 5.10.0 and the 5.11.0 -development releases. +=item * -=head1 Incompatible Changes +Magic was called twice in C, C<\&$x>, C and C. +These have all been fixed. -=head1 Core Enhancements +=item * -=head1 The C pragma +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]. -This pragma allows you to lexically disable or enable overloading -for some or all operations. (Yuval Kogman) +=item * -=head1 Modules and Pragmata +The line numbers for warnings inside C are now correct. -=head2 Pragmata Changes +=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 + +=item * + +Previously missing files from Unicode 5.1 Character Database are now included. + +=item * + +C is now honored when opening an anonymous temporary file + +=back + +=head1 New or Changed Diagnostics =over 4 -=item C +=item C -See L pragma"> above. +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 Utility Changes +=head1 Changed Internals + +=over 4 -=head1 Documentation +=item * -=head1 Performance Enhancements +TODO: C is gone. RVs are now stored in IVs -=head1 Installation and Configuration Improvements +=item * -=head1 Selected Bug Fixes +TODO: REGEXPs are first class + +=item * + +TODO: OOK is reworked, such that an OOKed scalar is PV not PVIV + +=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<-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) +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 -=head1 New or Changed Diagnostics +There is also a wrapper that takes constant strings, C. -=head1 Changed Internals +=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 C 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 * + +Smartmatch resolution tracing has been added as a new diagnostic. Use C<-DM> to +enable it. + + +=item * + +A new debugging flag C<-DB> now dumps subroutine definitions, leaving +C<-Dx> for its original purpose of dumping syntax trees. + +=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, F 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 -=head2 Platform Specific 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 * + +The following modules will be removed from the core distribution in a future +release, and should be installed from CPAN instead. Distributions on CPAN +which require these should add them to their prerequisites. The core versions +of these modules warnings will issue a deprecation warning. + +=over + +=item * + +C + +=item * + +C + +=item * + +C + +=back + +Currently support to install from CPAN without a I is C in CPAN +and CPANPLUS. This will be addressed before 5.12.0 ships. + +=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 + +=item * + +Removed vestigal support for Tenon Intersystems MachTen Unix layer for MacOS Classic. + +=item * + +Removed the port to Atari MiNT. It's a dead platform that hasn't had any love since 5.005. + + +=item * + +Deprecated numerous Perl 4-era libraries: + +F, F, F, F, F, +F, F, F, F, F, +F, F, F, F, +F, F, F, F, F, +F, F, F, F, F, +F, F, F, F, and +F are all now deprecated. Using them will incur a warning. + +=back + +=head1 Acknowledgements + +Some of the work in this release was funded by a TPF grant funded by +Dijkmat BV, The Netherlands. + +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://bugs.perl.org/ . There may also be +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 @@ -68,9 +2217,20 @@ 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 exhaustive details on what changed. +The F file for an explanation of how to view exhaustive details +on what changed. The F file for how to build Perl. @@ -79,3 +2239,5 @@ The F file for general stuff. The F and F files for copyright information. =cut + +