=head1 NAME
-perldelta - what is new for perl v5.21.8
+[ this is a template for a new perldelta file. Any text flagged as XXX needs
+to be processed before release. ]
+
+perldelta - what is new for perl v5.21.11
=head1 DESCRIPTION
-This document describes differences between the 5.21.7 release and the 5.21.8
+This document describes differences between the 5.21.10 release and the 5.21.11
release.
-If you are upgrading from an earlier release such as 5.21.6, first read
-L<perl5217delta>, which describes differences between 5.21.6 and 5.21.7.
+If you are upgrading from an earlier release such as 5.21.9, first read
+L<perl52110delta>, which describes differences between 5.21.9 and 5.21.10.
=head1 Notice
-With this release we are now in the contentious changes portion of the code
-freeze as we prepare for the next stable release of Perl 5.
+XXX Any important notices here
=head1 Core Enhancements
-=head2 The warnings pragma now supports warnings outside of "all"
+XXX New core language features go here. Summarize user-visible core language
+enhancements. Particularly prominent performance optimisations could go
+here, but most should go in the L</Performance Enhancements> section.
-Ever since perl v5.6.0 we've had no way of adding new warnings without
-retroactively adding them to all existing programs that used C<-w>,
-C<-W> or C<use warnings>.
+[ List each enhancement as a =head2 entry ]
-This caused us to not add new useful warnings out of fear that they
-might unduly burden users who just wanted to upgrade perl and didn't
-want to deal with a bunch of warnings from their existing code.
+=head1 Security
-We now support a way to have our cake and eat it too, and can add new
-warnings to the core going forward through other top-level warning
-categories. See L<the warnings documentation|warnings/Top-level
-warning categories & associated confusion> for details.
+XXX Any security-related notices go here. In particular, any security
+vulnerabilities closed should be noted here rather than in the
+L</Selected Bug Fixes> section.
-=head2 Non-Capturing Regular Expression Flag
+[ List each security issue as a =head2 entry ]
-Regular expressions now support a C</n> flag that disables capturing
-and filling in C<$1>, C<$2>, etc... inside of groups:
+=head1 Incompatible Changes
- "hello" =~ /(hi|hello)/n; # $1 is not set
+XXX For a release on a stable branch, this section aspires to be:
-This is equivalent to putting C<?:> at the beginning of every capturing group.
+ There are no changes intentionally incompatible with 5.XXX.XXX
+ If any exist, they are bugs, and we request that you submit a
+ report. See L</Reporting Bugs> below.
-See L<perlre/"n"> for more information.
+[ List each incompatible change as a =head2 entry ]
-=head2 C<prototype> with no arguments
+=head1 Deprecations
-C<prototype()> with no arguments now infers C<$_>. [perl #123514]
+XXX Any deprecated features, syntax, modules etc. should be listed here.
-=head2 C<use re 'strict'>
+=head2 Making all warnings fatal is discouraged
-This applies stricter syntax rules to regular expression patterns
-compiled within its scope, which hopefully will alert you to typos and
-other unintentional behavior that backwards-compatibility issues prevent
-us from doing in normal regular expression compilations. Because the
-behavior of this is subject to change in future Perl releases as we gain
-experience, using this pragma will raise a category
-C<experimental:re_strict> warning.
-See L<'strict' in re|re/'strict' mode>.
+The documentation for L<fatal warnings|warnings/Fatal Warnings> notes
+that C<< use warnings FATAL => 'all' >> is discouraged
+and provides stronger language about the risks of fatal warnings
+in general.
-=head2 New "const" subroutine attribute
+=head2 Module removals
-The "const" attribute can be applied to an anonymous subroutine. It causes
-it to be executed immediately when it is cloned. Its value is captured and
-used to create a new constant subroutine that is returned. This feature is
-experimental. See L<perlsub/Constant Functions>.
+XXX Remove this section if inapplicable.
-=head1 Incompatible Changes
+The following modules will be removed from the core distribution in a
+future release, and will at that time need to be installed from CPAN.
+Distributions on CPAN which require these modules will need to list them as
+prerequisites.
+
+The core versions of these modules will now issue C<"deprecated">-category
+warnings to alert you to this fact. To silence these deprecation warnings,
+install the modules in question from CPAN.
+
+Note that these are (with rare exceptions) fine modules that you are encouraged
+to continue to use. Their disinclusion from core primarily hinges on their
+necessity to bootstrapping a fully functional, CPAN-capable Perl installation,
+not usually on concerns over their design.
+
+=over
+
+=item XXX
+
+XXX Note that deprecated modules should be listed here even if they are listed
+as an updated module in the L</Modules and Pragmata> section.
+
+=back
+
+[ List each other deprecation as a =head2 entry ]
+
+=head1 Performance Enhancements
-=head2 sub signatures moved before attributes
+XXX Changes which enhance performance without changing behaviour go here.
+There may well be none in a stable release.
-The experimental sub signatures feature, as introduced in 5.20, parsed
-signatures after attributes. In this release, the positioning has been
-moved such that signatures occur in exactly the same positioning a
-prototype would be found.
+[ List each enhancement as a =item entry ]
+
+=over 4
+
+=item *
+
+XXX
+
+=back
=head1 Modules and Pragmata
=item *
-L<XXX> has been upgraded from version A.xx to B.yy.
+L<attributes> has been upgraded from version 0.26 to 0.27.
=item *
-L<attributes> has been upgraded from version 0.24 to 0.25.
+L<B> has been upgraded from version 1.57 to 1.58.
-Minor internal change only.
+=item *
+
+L<B::Deparse> has been upgraded from version 1.34 to 1.35.
=item *
-L<B> has been upgraded from version 1.54 to 1.55.
+L<Config::Perl::V> has been upgraded from version 0.23 to 0.24.
-A bug where, after an ithread creation or psuedofork, special/immortal SVs in
-the child ithread/psuedoprocess did not have the correct class of
-C<B::SPECIAL>, has been fixed.
+=item *
-The C<id> and C<outid> PADLIST methods have been added.
+L<Cwd> has been upgraded from version 3.55 to 3.56.
=item *
-L<B::Deparse> has been upgraded from version 1.31 to 1.32.
+L<ExtUtils::Miniperl> has been upgraded from version 1.04 to 1.05.
-Deparsing C<BEGIN { undef &foo }> with the B<-w> switch enabled started to
-emit 'uninitialized' warnings in Perl 5.14. This has been fixed.
+=item *
-Deparsing calls to subs with a C<(;+)> prototype resulted in an infinite
-loop. The C<(;$>) C<(_)> and C<(;_)> prototypes were given the wrong
-precedence, causing C<foo($a<$b)> to be deparsed without the parentheses.
+L<ExtUtils::ParseXS> has been upgraded from version 3.27 to 3.28.
=item *
-L<File::Glob> has been upgraded from version 1.23 to 1.24.
+L<ExtUtils::Typemaps> has been upgraded from version 3.25 to 3.28.
+
+=item *
-Avoid SvIV() expanding to call get_sv() three times in a few
-places. [perl #123606]
+L<File::Spec> has been upgraded from version 3.55 to 3.56.
=item *
-L<Module::Metadata> has been upgraded from version 1.000025 to 1.000026.
+L<if> has been upgraded from version 0.0603 to 0.0604.
=item *
-L<Safe> has been upgraded from version 2.38 to 2.39.
+L<IO::Socket::IP> has been upgraded from version 0.36 to 0.37.
+
+=item *
+
+L<Module::CoreList> has been upgraded from version 5.20150320 to 5.20150420.
+
+Updated to cover the latest releases of Perl.
+
+=item *
+
+L<perl5db.pl> has been upgraded from 1.48 to 1.49.
+
+The debugger would cause an assertion failure. [perl #124127]
+
+=item *
-C<reval> was not propagating void context properly.
+L<PerlIO::mmap> has been upgraded from version 0.013 to 0.014.
=item *
-L<SDBM_File> has been upgraded from version 1.12 to 1.13.
+L<utf8> has been upgraded from version 1.15 to 1.16.
+
+=item *
-Simplified the build process. [perl #123413]
+L<warnings> has been upgraded from version 1.31 to 1.32.
=back
=head1 Documentation
+XXX Changes to files in F<pod/> go here. Consider grouping entries by
+file and be sure to link to the appropriate page, e.g. L<perlfunc>.
+
=head2 New Documentation
-=head3 L<perlunicook>
+XXX Changes which create B<new> files in F<pod/> go here.
-This document, by Tom Christiansen, provides examples of handling Unicode in
-Perl.
+=head3 L<XXX>
-=head1 Diagnostics
+XXX Description of the purpose of the new file here
-The following additions or changes have been made to diagnostic output,
-including warnings and fatal error messages. For the complete list of
-diagnostic messages, see L<perldiag>.
+=head2 Changes to Existing Documentation
-=head2 New Diagnostics
+XXX Changes which significantly change existing files in F<pod/> go here.
+However, any changes to F<pod/perldiag.pod> should go in the L</Diagnostics>
+section.
-=head3 New Errors
+=head3 L<perlebcdic>
=over 4
=item *
-L<Bad symbol for scalar|perldiag/"Bad symbol for scalar">
-
-(P) An internal request asked to add a scalar entry to something that
-wasn't a symbol table entry.
-
-=item *
-
-L<:const is not permitted on named subroutines|perldiag/":const is not permitted on named subroutines">
-
-(F) The "const" attribute causes an anonymous subroutine to be run and
-its value captured at the time that it is cloned. Names subroutines are
-not cloned like this, so the attribute does not make sense on them.
+This document has been significantly updated in the light of recent
+improvements to EBCDIC support.
=back
-=head3 New Warnings
+=head3 L<perlhacktips>
=over 4
=item *
-L<:const is experimental|perldiag/":const is experimental">
+Documentation has been added illustrating the perils of assuming the contents of
+static memory pointed to by the return values of Perl wrappers for C library
+functions doesn't change.
+
+=back
-(S experimental::const_attr) The "const" attribute is experimental.
-If you want to use the feature, disable the warning with C<no warnings
-'experimental::const_attr'>, but know that in doing so you are taking
-the risk that your code may break in a future Perl version.
+=head3 L<perlvms>
+
+=over 4
=item *
-L<Non-finite repeat count does nothing|perldiag/"Non-finite repeat count does nothing">
+Out-of-date and/or incorrect material has been removed.
-(W numeric) You tried to execute the
-L<C<x>|perlop/Multiplicative Operators> repetition operator C<Inf> (or
-C<-Inf>) or C<NaN> times, which doesn't make sense.
+=back
-=item *
+=head1 Diagnostics
-L<Useless use of attribute "const"|perldiag/Useless use of attribute "const">
+The following additions or changes have been made to diagnostic output,
+including warnings and fatal error messages. For the complete list of
+diagnostic messages, see L<perldiag>.
-(W misc) The "const" attribute has no effect except
-on anonymous closure prototypes. You applied it to
-a subroutine via L<attributes.pm|attributes>. This is only useful
-inside an attribute handler for an anonymous subroutine.
+XXX New or changed warnings emitted by the core's C<C> code go here. Also
+include any changes in L<perldiag> that reconcile it to the C<C> code.
-=item *
+=head2 New Diagnostics
-L<Unusual use of %s in void context|perldiag/"Unusual use of %s in void context">
+XXX Newly added diagnostic messages go under here, separated into New Errors
+and New Warnings
-(W void_unusual) Similar to the "Useless use of %s in void context"
-warning, but only turned on by the top-level "pedantic" warning
-category, used for e.g. C<grep> in void context, which may indicate a
-bug, but could also just be someone using C<grep> for its side-effects
-as a loop.
+=head3 New Errors
-Enabled as part of "extra" warnings, not in the "all" category. See
-L<warnings> for details
+=over 4
=item *
-L<E<quot>use re 'strict'E<quot> is experimental|perldiag/"use re 'strict'" is experimental>
-
-(S experimental::re_strict) The things that are different when a regular
-expression pattern is compiled under C<'strict'> are subject to change
-in future Perl releases in incompatible ways. This means that a pattern
-that compiles today may not in a future Perl release. This warning is
-to alert you to that risk.
+XXX L<message|perldiag/"message">
-L<Wide character (U+%X) in %s|perldiag/"Wide character (U+%X) in %s">
+=back
-(W locale) While in a single-byte locale (I<i.e.>, a non-UTF-8
-one), a multi-byte character was encountered. Perl considers this
-character to be the specified Unicode code point. Combining non-UTF8
-locales and Unicode is dangerous. Almost certainly some characters
-will have two different representations. For example, in the ISO 8859-7
-(Greek) locale, the code point 0xC3 represents a Capital Gamma. But so
-also does 0x393. This will make string comparisons unreliable.
+=head3 New Warnings
-You likely need to figure out how this multi-byte character got mixed up
-with your single-byte locale (or perhaps you thought you had a UTF-8
-locale, but Perl disagrees).
+=over 4
=item *
-L<Both or neither range ends should be Unicode in regex; marked by E<lt>-- HERE in mE<sol>%sE<sol>|perldiag/"Both or neither range ends should be Unicode in regex; marked by <-- HERE in m/%s/">
+XXX L<message|perldiag/"message">
-(W regexp) (only under C<S<use re 'strict'>> or within C<(?[...])>)
+=back
-In a bracketed character class in a regular expression pattern, you
-had a range which has exactly one end of it specified using C<\N{}>, and
-the other end is specified using a non-portable mechanism. Perl treats
-the range as a Unicode range, that is, all the characters in it are
-considered to be the Unicode characters, and which may be different code
-points on some platforms Perl runs on. For example, C<[\N{U+06}-\x08]>
-is treated as if you had instead said C<[\N{U+06}-\N{U+08}]>, that is it
-matches the characters whose code points in Unicode are 6, 7, and 8.
-But that C<\x08> might indicate that you meant something different, so
-the warning gets raised.
+=head2 Changes to Existing Diagnostics
-=item *
+XXX Changes (i.e. rewording) of diagnostic messages go here
-L<Ranges of ASCII printables should be some subset of "0-9", "A-Z", or "a-z" in regex; marked by <-- HERE in mE<sol>%sE<sol>|perldiag/"Ranges of ASCII printables should be some subset of "0-9", "A-Z", or "a-z" in regex; marked by <-- HERE in mE<sol>%sE<sol>">
+=over 4
-(W regexp) (only under C<S<use re 'strict'>> or within C<(?[...])>)
+=item *
-Stricter rules help to find typos and other errors. Perhaps you didn't
-even intend a range here, if the C<"-"> was meant to be some other
-character, or should have been escaped (like C<"\-">). If you did
-intend a range, the one that was used is not portable between ASCII and
-EBCDIC platforms, and doesn't have an obvious meaning to a casual
-reader.
+XXX Describe change here
- [3-7] # OK; Obvious and portable
- [d-g] # OK; Obvious and portable
- [A-Y] # OK; Obvious and portable
- [A-z] # WRONG; Not portable; not clear what is meant
- [a-Z] # WRONG; Not portable; not clear what is meant
- [%-.] # WRONG; Not portable; not clear what is meant
- [\x41-Z] # WRONG; Not portable; not obvious to non-geek
+=back
-(You can force portablity by specifying a Unicode range, which means that
-the endpoints are specified by
-L<C<\N{...}>|perlrecharclass/Character Ranges>, but the meaning may
-still not be obvious.)
-The stricter rules require that ranges that start or stop with an ASCII
-character that is not a control have all their endpoints be the literal
-character, and not some escape sequence (like C<"\x41">), and the ranges
-must be all digits, or all uppercase letters, or all lowercase letters.
+=head1 Utility Changes
-=item *
+XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
+Most of these are built within the directory F<utils>.
-L<Ranges of digits should be from the same group in regex; marked by <-- HERE in mE<sol>%sE<sol>|perldiag/"Ranges of digits should be from the same group in regex; marked by <-- HERE in m/%s/">
+[ List utility changes as a =head2 entry for each utility and =item
+entries for each change
+Use L<XXX> with program names to get proper documentation linking. ]
-(W regexp) (only under C<S<use re 'strict'>> or within C<(?[...])>)
+=head2 L<XXX>
-Stricter rules help to find typos and other errors. You included a
-range, and at least one of the end points is a decimal digit. Under the
-stricter rules, when this happens, both end points should be digits in
-the same group of 10 consecutive digits.
+=over 4
=item *
-L<"%s" is more clearly written simply as "%s" in regex; marked by <-- HERE in mE<sol>%sE<sol>|perldiag/"%s" is more clearly written simply as "%s" in regex; marked by <-- HERE in mE<sol>%sE<sol>>
+XXX
-(W regexp) (only under C<S<use re 'strict'>> or within C<(?[...])>)
+=back
-You specified a character that has the given plainer way of writing it,
-and which is also portable to platforms running with different character
-sets.
+=head1 Configuration and Compilation
-=back
+XXX Changes to F<Configure>, F<installperl>, F<installman>, and analogous tools
+go here. Any other changes to the Perl build process should be listed here.
+However, any platform-specific changes should be listed in the
+L</Platform Support> section, instead.
-=head2 Changes to Existing Diagnostics
+[ List changes as a =item entry ].
=over 4
=item *
-The message
-L<Locale '%s' may not work well.%s|perldiag/"Locale '%s' may not work well.%s">
-is no longer raised unless the problemtatic locale is actually used in
-the Perl program. Previously it was raised if it merely was the
-underlying locale. All Perl programs have an underlying locale at all
-times, but something like a C<S<use locale>> is needed for that locale
-to actually have some effect. This message will not be raised when
-the underlying locale is hidden.
+XXX
=back
-=head1 Configuration and Compilation
+=head1 Testing
+
+XXX Any significant changes to the testing of a freshly built perl should be
+listed here. Changes which create B<new> files in F<t/> go here as do any
+large changes to the testing harness (e.g. when parallel testing was added).
+Changes to existing files in F<t/> aren't worth summarizing, although the bugs
+that they represent may be covered elsewhere.
+
+[ List each test improvement as a =item entry ]
=over 4
=item *
-pthreads and lcl will be linked by default if present. This allows XS modules
-that require threading to work on non-threaded perls. Note that you must still
-pass C<-Dusethreads> if you want a threaded perl.
+XXX
=back
-=head1 Testing
+=head1 Platform Support
-=over 4
+XXX Any changes to platform support should be listed in the sections below.
-=item *
+[ Within the sections, list each platform as a =item entry with specific
+changes as paragraphs below it. ]
-A new test script, F<bigmem/subst.t>, has been added to test memory usage of
-subst on very large strings.
+=head2 New Platforms
-=item *
+XXX List any platforms that this version of perl compiles on, that previous
+versions did not. These will either be enabled by new files in the F<hints/>
+directories, or new subdirectories and F<README> files at the top level of the
+source tree.
-A new test script, F<op/anonconst.t>, has been added to test experimental
-:const subroutines.
+=over 4
-=item *
+=item XXX-some-platform
-A new test script, F<re/reg_nocapture.t>, has been added to test the new
-C</n> regexp flag.
+XXX
=back
-=head1 Platform Support
+=head2 Discontinued Platforms
-=head2 Platform-Specific Notes
+XXX List any platforms that this version of perl no longer compiles on.
=over 4
-=item Win32
+=item XXX-some-platform
-=over 4
+XXX
-=item *
+=back
-Previously, on Visual C++ for Win64 built Perls only, when compiling every Perl
-XS module (including CPAN ones) and Perl aware .c file with a 64 bit Visual C++,
-would uncondtionally have around a dozen warnings from hv_func.h. These
-warnings have been silenced. GCC all bitness and Visual C++ for Win32 were
-not affected.
+=head2 Platform-Specific Notes
-=item *
+XXX List any changes for specific platforms. This could include configuration
+and compilation changes or changes in portability/compatibility. However,
+changes within modules for platforms should generally be listed in the
+L</Modules and Pragmata> section.
-Support for building without PerlIO has been removed from the Windows
-makefiles. Non-PerlIO builds were all but deprecated in Perl 5.18.0 and are
-already not supported by F<Configure> on POSIX systems.
+=over 4
-=item *
+=item Win32
-Between 2 and 6 ms and 7 I/O calls have been saved per attempt to open a perl
-module for each path in C<@INC>.
+F<miniperl.exe> is now built with C<-fno-strict-aliasing>, allowing
+64-bit builds to complete on GCC 4.8. [perl #123976]
-=back
+C<test-prep> again depends on C<test-prep-gcc> for GCC builds. [perl
+#124221]
=back
=item *
-Added Perl_sv_get_backrefs() to determine if an SV is a weak-referent.
-
-Function either returns an SV * of type AV, which contains the set of
-weakreferences which reference the passed in SV, or a simple RV * which
-is the only weakref to this item.
-
-=back
-
-=head1 Selected Bug Fixes
+5.21.2 introduced a new build option, C<-DPERL_OP_PARENT>, which causes
+the last C<op_sibling> pointer to refer back to the parent rather than
+being C<NULL>, and where instead a new flag indicates the end of the
+chain. In this release, the new implementation has been revised; in
+particular:
=over 4
=item *
-A bug in regular expression patterns that could lead to segfaults and
-other crashes has been fixed. This occurred only in patterns compiled
-with C<"/i">, while taking into account the current POSIX locale (this usually
-means they have to be compiled within the scope of C<S<"use locale">>),
-and there must be a string of at least 128 consecutive bytes to match.
-[perl #123539]
+On C<PERL_OP_PARENT> builds, the C<op_sibling> field has been renamed
+C<op_sibparent> to reflect its new dual purpose. Since the intention is that
+this field should primarily be accessed via macros, this change should be
+transparent for code written to work under C<PERL_OP_PARENT>.
=item *
-C<s///> now works on very long strings instead of dying with 'Substitution
-loop'. [perl #103260] [perl #123071]
+The newly-introduced C<op_lastsib> flag bit has been renamed C<op_moresib>
+and its logic inverted; i.e. it is initialised to zero in a new op, and is
+changed to 1 when an op gains a sibling.
=item *
-C<gmtime> no longer crashes with not-a-number values. [perl #123495]
+The function C<Perl_op_parent> is now only available on C<PERL_OP_PARENT>
+builds. Using it on a plain build will be a compile-timer error.
=item *
-C<\()> (reference to an empty list) and C<y///> with lexical $_ in scope
-could do a bad write past the end of the stack. They have been fixed
-to extend the stack first.
+Three new macros, C<OpMORESIB_set>, C<OpLASTSIB_set>, C<OpMAYBESIB_set>
+have been added, which are intended to be be a low-level portable way to
+set C<op_sibling> / C<op_sibparent> while also updating C<op_moresib>.
+The first sets the sibling pointer to a new sibling, the second makes the
+op the last sibling, and the third conditionally does the first or second
+action. The C<op_sibling_splice()> function is retained as a higher-level
+interface that can also maintain consistency in the parent at the same time
+(e.g. by updating C<op_first> and C<op_last> where appropriate).
=item *
-C<prototype()> with no arguments used to read the previous item on the
-stack, so C<print "foo", prototype()> would print foo's prototype. It has
-been fixed to infer $_ instead. [perl #123514]
+The macro C<OpSIBLING_set>, added in 5.21.2, has been removed. It didn't
+manipulate C<op_moresib> and has been superseded by C<OpMORESIB_set> et
+al.
=item *
-Some cases of lexical state subs inside predeclared subs could crash but no
-longer do.
+The C<op_sibling_splice> function now accepts a null C<parent> argument
+where the splicing doesn't affect the first or last ops in the sibling
+chain, and thus where the parent doesn't need to be updated accordingly.
-=item *
+=back
+
+
+=back
+
+=head1 Selected Bug Fixes
+
+XXX Important bug fixes in the core language are summarized here. Bug fixes in
+files in F<ext/> and F<lib/> are best summarized in L</Modules and Pragmata>.
-Some cases of nested lexical state subs inside anonymous subs could cause
-'Bizarre copy' errors or possibly even crash.
+[ List each fix as a =item entry ]
+
+=over 4
=item *
-When trying to emit warnings, perl's default debugger (F<perl5db.pl>) was
-sometimes giving 'Undefined subroutine &DB::db_warn called' instead. This
-bug, which started to occur in Perl 5.18, has been fixed. [perl #123553]
+C<pack("D", $x)> and C<pack("F", $x)> now zero the padding on x86 long
+double builds. GCC 4.8 and later, under some build options, would
+either overwrite the zero-initialized padding, or bypass the
+initialized buffer entirely. This caused F<op/pack.t> to fail. [perl
+#123971]
=item *
-Certain syntax errors in substitutions, such as C<< s/${<>{})// >>, would
-crash, and had done so since Perl 5.10. (In some cases the crash did not
-start happening till 5.16.) The crash has, of course, been fixed.
-[perl #123542]
+Extending an array cloned from a parent thread could result in
+"Modification of a read-only value attempted" errors when attempting
+to modify the new elements. [perl #124127]
+
+=back
+
+=head1 Known Problems
+
+XXX Descriptions of platform agnostic bugs we know we can't fix go here. Any
+tests that had to be C<TODO>ed for the release would be noted here. Unfixed
+platform specific bugs also go here.
+
+[ List each fix as a =item entry ]
+
+=over 4
=item *
-A repeat expression like C<33 x ~3> could cause a large buffer
-overflow since the new output buffer size was not correctly handled by
-SvGROW(). An expression like this now properly produces a memory wrap
-panic. [perl 123554]
+XXX
+
+=back
+
+=head1 Errata From Previous Releases
+
+=over 4
=item *
-C<< formline("@...", "a"); >> would crash. The C<FF_CHECKNL> case in
-pp_formline() didn't set the pointer used to mark the chop position,
-which led to the C<FF_MORE> case crashing with a segmentation fault.
-This has been fixed. [perl #123538]
+XXX Add anything here that we forgot to add, or were mistaken about, in
+the perldelta of a previous release.
=back
+=head1 Obituary
+
+XXX If any significant core contributor has died, we've added a short obituary
+here.
+
=head1 Acknowledgements
XXX Generate this with:
- perl Porting/acknowledgements.pl v5.21.7..HEAD
+ perl Porting/acknowledgements.pl v5.21.10..HEAD
=head1 Reporting Bugs
https://perl5.git.perl.org / perl5.git / blobdiff