=encoding utf8
-=for todo
-5204593b74eb sv.c: Make sv_pvn_force_flags guard against SV_UNDEF_RETURNS_NULL.
-dad26a174010 Since the HTML files generated by pod2html claim to have a utf-8 charset, actually write the files out using utf-8. This is a fix for RT #111446.
-28333232a1c7 Don’t localise CopSTASH(&PL_compiling) in newCONSTSUB
-c947b31cf142 Do away with stashpv_hvname_match
-d0279c7ce493 Fix bad assertions in pp_ctl.c:pp_caller
-df826430da0d make TRIE nodes "absorb" NOTHING->EXACT sequences
-3b6759a6b102 optimise (?:|) and related NOTHING like constructs out of the compiled optree
-5435c3759c45 Experimentally Use Unicode 6.2 beta
-4a808ed163df [perl #111610] Trouble with XS-APItest/t/clone-with-stack.t
-1db94eebfa93 Quieten B::Deparse warnings (fixes #113464).
-72a866183393 reorganize perlcheat
-9a62b98f29d2 gv.c: Don’t ENTER/LEAVE unnecessarily
-ee1b3814fd18 gv.c: Remove mro_method_changed_in() from gv_init
-a3c74922a705 Rmv mro_method_changed_in call on stub upgraded to const
-186a5ba82d58 Don’t create pads for sub stubs
-7ad40bcb0a19 Don’t call mro_method_changed_in after newCONSTSUB
-83b195e49dd1 ensure correctness if sv_2mortal modifies errno
-
=head1 NAME
-perldelta - what is new for perl v5.17.1
+[ 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.17.3
=head1 DESCRIPTION
-This document describes differences between the 5.17.0 release and
-the 5.17.1 release.
+This document describes differences between the 5.17.2 release and the 5.17.3
+release.
+
+If you are upgrading from an earlier release such as 5.17.1, first read
+L<perl5172delta>, which describes differences between 5.17.1 and 5.17.2.
+
+=head1 Notice
-If you are upgrading from an earlier release such as 5.16.0, first read
-L<perl5170delta>, which describes differences between 5.16.0 and
-5.17.0.
+XXX Any important notices here
=head1 Core Enhancements
-=head2 More CORE:: subs
+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.
-Several more built-in functions have been added as subroutines to the
-CORE:: namespace, namely, those non-overridable keywords that can be
-implemented without custom parsers: C<defined>, C<delete>, C<exists>,
-C<glob>, C<pos>, C<protoytpe>, C<scalar>, C<split>, C<study>, and C<undef>.
+[ List each enhancement as a =head2 entry ]
-As some of these have prototypes, C<prototype('CORE::...')> has been
-changed to not make a distinction between overridable and non-overridable
-keywords. This is to make C<prototype('CORE::pos')> consistent with
-C<prototype(&CORE::pos)>.
+=head2 Computed Labels
-=head1 Incompatible Changes
+The loop controls C<next>, C<last> and C<redo>, and the special C<dump>
+operator, now allow arbitrary expressions to be used to compute labels at
+run time. Previously, any argument that was not a constant was treated as
+the empty string.
+
+=head1 Security
+
+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 C</(?{})/> and C</(??{}> have been heavily reworked.
+[ List each security issue as a =head2 entry ]
-The implementation of this feature has been almost completely rewritten.
-Although its main intent is to fix bugs, some behaviours, especially
-related to the scope of lexical variables, will have changed. This is
-described more fully in the L</Selected Bug Fixes> section.
+=head1 Incompatible Changes
-=head2 C<\N{BELL}> now refers to U+1F514 instead of U+0007
+[ List each incompatible change as a =head2 entry ]
-Unicode 6.0 reused the name "BELL" for a different code point than it
-traditionally had meant. Since Perl v5.14, use of this name still
-referred to U+0007, but would raise a deprecated warning. Now, "BELL"
-refers to U+1F514, and the name for U+0007 is "ALERT". All the
-functions in L<charnames> have been correspondingly updated.
+=head2 C<$ENV{foo} = undef> deletes value from environ, like C<delete $ENV{foo}>
-=head2 Alphanumeric operators must now be separated from the closing
-delimiter of regular expressions
+This facilitates use of C<local()> with C<%ENV> entries. In previous
+versions of Perl, C<undef> was converted to the empty string.
-You may no longer write something like:
+=head2 Defined values stored in environment are forced to byte strings
- m/a/and 1
+A value stored in an environment variable has always been stringified. In
+this release, it is converted to be only a byte string. First, it is forced
+to be a only a string. Then if the string is utf8 and the equivalent of
+C<utf8::downgrade()> works, that result is used; otherwise, the equivalent of
+C<utf8::encode()> is used, and a warning is issued about wide characters
+(L</Diagnostics>).
-Instead you must write
+=head2 C<given> now aliases the global C<$_>
- m/a/ and 1
+Instead of assigning to an implicit lexical C<$_>, C<given> now makes the
+global C<$_> an alias for its argument, just like C<foreach>. However, it
+still uses lexical C<$_> if there is lexical C<$_> in scope (again, just like
+C<foreach>).
-with whitespace separating the operator from the closing delimiter of
-the regular expression. Not having whitespace has resulted in a
-deprecated warning since Perl v5.14.0.
+=head1 Deprecations
-=head2 C<require> dies for unreadable files
+XXX Any deprecated features, syntax, modules etc. should be listed here. In
+particular, deprecated modules should be listed here even if they are listed as
+an updated module in the L</Modules and Pragmata> section.
-When C<require> encounters an unreadable file, it now dies. It used to
-ignore the file and continue searching the directories in @INC
-[perl #113422].
+[ List each deprecation as a =head2 entry ]
=head1 Performance Enhancements
+XXX Changes which enhance performance without changing behaviour go here.
+There may well be none in a stable release.
+
+[ List each enhancement as a =item entry ]
+
=over 4
=item *
-The C<x> repetition operator is now folded to a single constant at compile
-time if called in scalar context with constant operands and no parentheses
-around the left operand.
+XXX
=back
=head1 Modules and Pragmata
-=head2 Updated Modules and Pragmata
+XXX All changes to installed files in F<cpan/>, F<dist/>, F<ext/> and F<lib/>
+go here. If Module::CoreList is updated, generate an initial draft of the
+following sections using F<Porting/corelist-perldelta.pl>, which prints stub
+entries to STDOUT. Results can be pasted in place of the '=head2' entries
+below. A paragraph summary for important changes should then be added by hand.
+In an ideal world, dual-life modules would have a F<Changes> file that could be
+cribbed.
+
+[ Within each section, list entries as a =item entry ]
+
+=head2 New Modules and Pragmata
=over 4
=item *
-L<ExtUtils::CBuilder> has been upgraded from version 0.280206 to 0.280208.
+XXX
-Manifest files are now correctly embedded for those versions of VC++ which
-make use of them. [perl #111782, #111798].
+=back
+
+=head2 Updated Modules and Pragmata
+
+=over 4
=item *
-L<B> has been upgraded from version 1.35 to 1.36.
+L<B> has been upgraded from version 1.36 to 1.37. All C<CVf_*> and C<GVf_*>
+and more SV-related flag values are now provided as constants in the C<B::>
+namespace and available for export. The default export list has not changed.
-C<B::COP::stashlen> has been replaced with C<B::COP::stashoff>.
+=item *
-C<B::COP::stashpv> now supports UTF8 package names and embedded NULs.
+L<B::Concise> has been upgraded from version 1.91 to 1.92. XXX Add change
+notes.
=item *
-L<Class::Struct> has been upgraded from version 0.63 to 0.64.
+L<B::Deparse> has been upgraded from version 1.15 to 1.16. It now deparses
+loop controls with the correct precedence.
+
+=item *
-The constructor now respects overridden accessor methods [perl #29230].
+L<Compress::Raw::Bzip2> has been upgraded from version 2.05201 to 2.055. XXX
+Add change notes.
=item *
-L<DynaLoader> has been upgraded from version 1.14 to 1.15.
+L<Compress::Raw::Zlib> has been upgraded from version 2.05401 to 2.056. XXX
+Add change notes.
-This is due to a minor code change in the XS for the VMS implementation.
+=item *
+
+L<Data::Dumper> has been upgraded from version 2.135_06 to 2.135_07. It has
+been optimized to only build a seen-scalar hash as necessary, thereby speeding
+up serialization drastically.
=item *
-L<File::DosGlob> has been upgraded from version 1.07 to 1.08.
+L<Devel::Peek> has been upgraded from version 1.08 to 1.09. XXX Add change
+notes.
+
+=item *
-There are no visible changes, only minor internal refactorings.
+L<Encode> has been upgraded from version 2.44 to 2.46. XXX Add change notes.
=item *
-L<File::Spec::Unix> has been upgraded from version 3.39_02 to 3.39_03.
+L<IO::Compress> has been upgraded from version 2.052 to 2.055. XXX Add change
+notes.
+
+=item *
-C<abs2rel> could produce incorrect results when given two relative paths or
-the root directory twice [perl #111510].
+L<Module::Build> has been upgraded from version 0.40 to 0.4002. XXX Add change
+notes.
=item *
-L<IO> has been upgraded from version 1.25_06 to 1.25_07.
+L<Module::CoreList> has been upgraded from version 2.69 to 2.70. XXX Add
+change notes.
-C<sync()> can now be called on read-only file handles [perl #64772].
+=item *
+
+L<Module::Load::Conditional> has been upgraded from version 0.50 to 0.54. XXX
+Add change notes.
=item *
-L<Pod::Html> has been upgraded from version 1.15_02 to 1.16.
+L<Module::Metadata> has been upgraded from version 1.000009 to 1.000010. XXX
+Add change notes.
+
+=item *
-The option C<--libpods> has been reinstated. It is deprecated, and its use
-does nothing other than issue a warning that it is no longer supported.
+L<re> has been upgraded from version 0.21 to 0.22. XXX Add change notes.
=item *
-L<Unicode::UCD> has been upgraded from version 0.43 to 0.44.
+L<Storable> has been upgraded from version 2.37 to 2.38. It can now freeze
+and thaw vstrings correctly. This causes a slight incompatible change in
+the storage format, so the format version has increased to 2.9.
-This adds a function L<all_casefolds()|Unicode::UCD/all_casefolds()>
-that returns all the casefolds.
+=item *
+
+L<Time::Local> has been upgraded from version 1.2000 to 1.2300. XXX Add change
+notes.
=item *
-L<Scalar::Util> has been upgraded from version 1.23 to version 1.25.
+L<Unicode::UCD> has been upgraded from version 0.44 to 0.45. XXX Add change
+notes.
-=back
+=item *
-=head1 Documentation
+L<Win32CORE> has been upgraded from version 0.02 to 0.03. XXX Add change
+notes.
-=head2 Changes to Existing Documentation
+=back
-=head3 L<perlfaq>
+=head2 Removed Modules and Pragmata
=over 4
=item *
-L<perlfaq> has been synchronised with version 5.0150040 from C<CPAN>.
+XXX
=back
-=head1 Diagnostics
+=head1 Documentation
-=head2 Removals of Diagnostics
+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>.
-=over 4
+=head2 New Documentation
-=item *
+XXX Changes which create B<new> files in F<pod/> go here.
+
+=head3 L<XXX>
+
+XXX Description of the purpose of the new file here
+
+=head2 Changes to Existing Documentation
+
+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.
-The "Runaway prototype" warning that occurs in bizarre cases has been
-removed as being unhelpful and inconsistent.
+=head3 L<perlfunc>, L<perlop>
+
+=over 4
=item *
-The "Not a format reference" error has been removed, as the only case in
-which it could be triggered was a bug.
+Loop control verbs (C<dump>, C<goto>, C<next>, C<last> and C<redo>) have
+always had the same precedence as assignment operators, but this was never
+documented until now.
=back
-=head1 Platform Support
+=head1 Diagnostics
-=head2 Platform-Specific Notes
+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>.
+
+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.
-XXX note fails on win2k and vms
+=head2 New Diagnostics
+
+XXX Newly added diagnostic messages go under here, separated into New Errors
+and New Warnings
+
+=head3 New Errors
=over 4
-=item Win32
+=item *
+
+L<Unterminated delimiter for here document|perldiag/"Unterminated delimiter for here document">
-C<link> on Win32 now attempts to set C<$!> to more appropriate values
-based on the Win32 API error code. [perl #112272]
+This message now occurs when a here document label has an initial quotation
+mark but the final quotation mark is missing.
-Perl no longer mangles the environment block, e.g. when launching a new
-sub-process, when the environment contains non-ASCII characters. Known
-problems still remain, however, when the environment contains characters
-outside of the current ANSI codepage (e.g. see the item about Unicode in
-C<%ENV> in L<http://perl5.git.perl.org/perl.git/blob/HEAD:/Porting/todo.pod>).
-[perl #113536]
+This replaces a bogus and misleading error message about not finding the
+label itself [perl #114104].
=back
-=head1 Internal Changes
+=head3 New Warnings
=over 4
=item *
-The C<study> function was made a no-op in 5.16. It was simply disabled via
-a C<return> statement; the code was left in place. Now the code supporting
-what C<study> used to do has been removed.
+L<Wide character in setenv|perldiag/"Wide character in setenv">
-=item *
+Attempts to put wide characters into environment variables via C<%ENV> now
+provoke this warning.
+
+=back
-Under threaded perls, there is no longer a separate PV allocated for every
-COP to store its package name (C<< cop->stashpv >>). Instead, there is an
-offset (C<< cop->stashoff >>) into the new C<PL_stashpad> array, which
-holds stash pointers.
+=head2 Changes to Existing Diagnostics
-=item *
+XXX Changes (i.e. rewording) of diagnostic messages go here
-In the pluggable regex API, the C<regexp_engine> struct has acquired a new
-field C<op_comp>, which is currently just for perl's internal use, and
-should be initialised to NULL by other regex plugin modules.
+=over 4
=item *
-A new function C<alloccoptash> has been added to the API, but is considered
-experimental. See L<perlapi>.
+XXX Describe change here
=back
-=head1 Selected Bug Fixes
+=head1 Utility Changes
-=over 4
+XXX Changes to installed programs such as F<perlbug> and F<xsubpp> go here.
+Most of these are built within the directories F<utils> and F<x2p>.
-=item *
+[ List utility changes as a =head3 entry for each utility and =item
+entries for each change
+Use L<XXX> with program names to get proper documentation linking. ]
-The implementation of code blocks in regular expressions, such as C<(?{})>
-and C<(??{})> has been heavily reworked to eliminate a whole slew of bugs.
-The main user-visible changes are:
+=head3 L<XXX>
=over 4
=item *
-Code blocks within patterns are now parsed in the same pass as the
-surrounding code; in particular it is no longer necessary to have balanced
-braces: this now works:
-
- /(?{ $x='{' })/
+XXX
-This means that this error message is longer generated:
-
- Sequence (?{...}) not terminated or not {}-balanced in regex
+=back
-but a new error may be seen:
+=head1 Configuration and Compilation
- Sequence (?{...}) not terminated with ')'
+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.
-In addition, literal code blocks within run-time patterns are only
-compiled once, at perl compile-time:
+[ List changes as a =item entry ].
- for my $p (...) {
- # this 'FOO' block of code is compiled once,
- # at the same time as the surrounding 'for' loop
- /$p{(?{FOO;})/;
- }
+=over 4
=item *
-Lexical variables are now sane as regards scope, recursion and closure
-behaviour. In particular, C</A(?{B})C/> behaves (from a closure viewpoint)
-exactly like C</A/ && do { B } && /C/>, while C<qr/A(?{B})C/> is like
-C<sub {/A/ && do { B } && /C/}>. So this code now works how you might
-expect, creating three regexes that match 0, 1, and 2:
+XXX
- for my $i (0..2) {
- push @r, qr/^(??{$i})$/;
- }
- "1" =~ $r[1]; # matches
+=back
-=item *
+=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.
-The C<use re 'eval'> pragma is now only required for code blocks defined
-at runtime; in particular in the following, the text of the C<$r> pattern is
-still interpolated into the new pattern and recompiled, but the individual
-compiled code-blocks within C<$r> are reused rather than being recompiled,
-and C<use re 'eval'> isn't needed any more:
+[ List each test improvement as a =item entry ]
- my $r = qr/abc(?{....})def/;
- /xyz$r/;
+=over 4
=item *
-Flow control operators no longer crash. Each code block runs in a new
-dynamic scope, so C<next> etc. will not see any enclosing loops and
-C<caller> will not see any calling subroutines. C<return> returns a value
-from the code block, not from any enclosing subroutine.
+XXX
-=item *
+=back
-Perl normally caches the compilation of run-time patterns, and doesn't
-recompile if the pattern hasn't changed; but this is now disabled if
-required for the correct behaviour of closures; for example:
+=head1 Platform Support
- my $code = '(??{$x})';
- for my $x (1..3) {
- # recompile to see fresh value of $x each time
- $x =~ /$code/;
- }
+XXX Any changes to platform support should be listed in the sections below.
+[ Within the sections, list each platform as a =item entry with specific
+changes as paragraphs below it. ]
-=item *
+=head2 New Platforms
-The C</msix> and C<(?msix)> etc. flags are now propagated into the return
-value from C<(??{})>; this now works:
+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.
- "AB" =~ /a(??{'b'})/i;
+=over 4
-=item *
+=item XXX-some-platform
-Warnings and errors will appear to come from the surrounding code (or for
-run-time code blocks, from an eval) rather than from an C<re_eval>:
+XXX
- use re 'eval'; $c = '(?{ warn "foo" })'; /$c/;
- /(?{ warn "foo" })/;
+=back
+
+=head2 Discontinued Platforms
-formerly gave:
+XXX List any platforms that this version of perl no longer compiles on.
- foo at (re_eval 1) line 1.
- foo at (re_eval 2) line 1.
+=over 4
-and now gives:
+=item XXX-some-platform
- foo at (eval 1) line 1.
- foo at /some/prog line 2.
+XXX
=back
-=item *
+=head2 Platform-Specific Notes
-Perl now works as well as can be expected on all releases of Unicode so
-far. In v5.16, it worked on Unicodes 6.0 and 6.1, but there were
-various bugs for earlier releases; the older the release the more
-problems.
+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.
-=item *
+=over 4
-C<vec> no longer produces "uninitialized" warnings in lvalue context
-[perl #9423].
+=item XXX-some-platform
-=item *
+XXX
-An optimisation involving fixed strings in regular expressions could cause
-a severe performance penalty in edge cases. This has been fixed
-[perl #76546].
+=back
-=item *
+=head1 Internal Changes
-The "Can't find an opnumber" message that C<prototype> produces when passed
-a string like "CORE::nonexistent_keyword" now passes UTF8 and embedded
-NULs through unchanged [perl #97478].
+XXX Changes which affect the interface available to C<XS> code go here. Other
+significant internal changes for future core maintainers should be noted as
+well.
-=item *
+[ List each change as a =item entry ]
-C<prototype> now treats magical variables like C<$1> the same way as
-non-magical variables when checking for the CORE:: prefix, instead of
-treating them as subroutine names.
+=over 4
=item *
-Under threaded perls, a runtime code block in a regular expression could
-corrupt the package name stored in the op tree, resulting in bad reads
-in C<caller>, and possibly crashes [perl #113060].
+XXX
-=item *
+=back
-Referencing a closure prototype (C<\&{$_[1]}> in an attribute handler for a
-closure) no longer results in a copy of the subroutine (or assertion
-failures on debugging builds).
+=head1 Selected Bug Fixes
-=item *
+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>.
-C<eval '__PACKAGE__'> now returns the right answer on threaded builds if
-the current package has been assigned over (as in
-C<*ThisPackage:: = *ThatPackage::>) [perl #78742].
+[ List each fix as a =item entry ]
+
+=over 4
=item *
-If a package is deleted by code that it calls, it is possible for C<caller>
-to see a stack frame belonging to that deleted package. C<caller> could
-crash if the stash's memory address was reused for a scalar and a
-substitution was performed on the same scalar [perl #113486].
+C<\w> now matches the code points U+200C (ZERO WIDTH NON-JOINER) and
+U+200D (ZERO WIDTH JOINER). C<\W> no longer matches these. This change
+is because Unicode corrected their definition of what C<\w> should match.
=item *
-C<UNIVERSAL::can> no longer treats its first argument differently
-depending on whether it is a string or number internally.
+C<dump LABEL> no longer leaks its label.
=item *
-C<open> with "<&" for the mode checks to see whether the third argument is
-a number, in determining whether to treat it as a file descriptor or a
-handle name. Magical variables like C<$1> were always failing the numeric
-check and being treated as handle names.
+Constant folding no longer changes the behaviour of functions like C<stat()>
+and C<truncate()> that can take either filenames or handles.
+C<stat 1 ? foo : bar> nows treats its argument as a file name (since it is
+an arbitrary expression), rather than the handle "foo".
=item *
-C<warn>'s handling of magical variables (C<$1>, ties) has undergone several
-fixes. FETCH is only called once now on a tied argument or a tied C<$@>
-[perl #97480]. Tied variables returning objects that stringify as "" are
-no longer ignored. A tied C<$@> that happened to return a reference the
-I<previous> time is was used is no longer ignored.
+C<truncate FOO, $len> no longer falls back to treating "FOO" as a file name
+if the filehandle has been deleted. This was broken in Perl 5.16.0.
=item *
-C<warn ""> now treats C<$@> with a number in it the same way, regardless of
-whether it happened via C<$@=3> or C<$@="3">. It used to ignore the
-former. Now it appends "\t...caught", as it has always done with
-C<$@="3">.
+Subroutine redefinitions after sub-to-glob and glob-to-glob assignments no
+longer cause double frees or panic messages.
=item *
-Numeric operators on magical variables (e.g., S<C<$1 + 1>>) used to use
-floating point operations even where integer operations were more appropriate,
-resulting in loss of accuracy on 64-bit platforms [perl #109542].
+C<s///> now turns vstrings into plain strings when performing a
+substitution, even if the resulting string is the same (C<s/a/a/>).
=item *
-Unary negation no longer treats a string as a number if the string happened
-to be used as a number at some point. So, if C<$x> contains the string "dogs",
-C<-$x> returns "-dogs" even if C<$y=0+$x> has happened at some point.
+Prototype mismatch warnings no longer erroneously treat constant subs as
+having no prototype when they actually have "".
=item *
-In Perl 5.14, C<-'-10'> was fixed to return "10", not "+10". But magical
-variables (C<$1>, ties) were not fixed till now [perl #57706].
+Constant subroutines and forward declarations no longer prevent prototype
+mismatch warnings from omitting the sub name.
=item *
-Unary negation now treats strings consistently, regardless of the internal
-UTF8 flag.
+C<undef> on a subroutine now clears call checkers.
=item *
-A regression introduced in Perl v5.16.0 involving
-C<tr/I<SEARCHLIST>/I<REPLACEMENTLIST>/> has been fixed. Only the first
-instance is supposed to be meaningful if a character appears more than
-once in C<I<SEARCHLIST>>. Under some circumstances, the final instance
-was overriding all earlier ones. [perl #113584]
+The C<ref> operator started leaking memory on blessed objects in Perl
+5.16.0. This has been fixed [perl #114340].
-=item *
+=back
-Regular expressions like C<qr/\87/> previously silently inserted a NUL
-character, thus matching as if it had been written C<qr/\00087/>. Now it
-matches as if it had been written as C<qr/87/>, with a message that the
-sequence C<"\8"> is unrecognized.
+=head1 Known Problems
-=item *
+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 ]
-C<__SUB__> now works in special blocks (BEGIN, END, etc.).
+=over 4
=item *
-Thread creation on Windows could theoretically result in a crash if done
-inside a BEGIN block. It still does not work properly, but it no longer
-crashes [perl #111610].
+XXX
=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.17.0..HEAD
+ perl Porting/acknowledgements.pl v5.17.2..HEAD
=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 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 L<perlbug>
-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<perl -V>, will be sent off to perlbug@perl.org to be
-analysed by the Perl porting team.
+If you believe you have an unreported bug, please run the L<perlbug> 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<perl -V>,
+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 will be able
-to help assess the impact of issues, figure out a resolution, and help
+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 will 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.
+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<Changes> file for an explanation of how to view exhaustive details
-on what changed.
+The F<Changes> file for an explanation of how to view exhaustive details on
+what changed.
The F<INSTALL> file for how to build Perl.
https://perl5.git.perl.org / perl5.git / blobdiff