=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
+7ad40bcb0a19 Don’t call mro_method_changed_in after newCONSTSUB
83b195e49dd1 ensure correctness if sv_2mortal modifies errno
=head1 NAME
-[ 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.1
=head1 DESCRIPTION
L<perl5170delta>, which describes differences between 5.16.0 and
5.17.0.
-=head1 Notice
-
-XXX Any important notices here
-
=head1 Core Enhancements
-XXX New core language features go here. Summarise user-visible core language
-enhancements. Particularly prominent performance optimisations could go
-here, but most should go in the L</Performance Enhancements> section.
-
-[ List each enhancement as a =head2 entry ]
-
=head2 More CORE:: subs
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>, C<undef>,
+C<glob>, C<pos>, C<protoytpe>, C<scalar>, C<split>, C<study>, and C<undef>.
As some of these have prototypes, C<prototype('CORE::...')> has been
-changed not to make a distinction between overridable and non-overridable
+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)>.
-=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.
-
-[ List each security issue as a =head2 entry ]
-
=head1 Incompatible Changes
-XXX For a release on a stable branch, this section aspires to be:
-
- 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.
-
=head2 C</(?{})/> and C</(??{}> have been heavily reworked.
-The implementation of this feature has been almost completely written.
-Although its main intent is is to fix bugs, some behaviours, especially
+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.
functions in L<charnames> have been correspondingly updated.
=head2 Alphanumeric operators must now be separated from the closing
-delimter of regular expressions
+delimiter of regular expressions
You may no longer write something like:
ignore the file and continue searching the directories in @INC
[perl #113422].
-=head1 Deprecations
-
-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.
-
-[ 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 *
=head1 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 *
-
-XXX
-
-=back
-
=head2 Updated Modules and Pragmata
=over 4
L<ExtUtils::CBuilder> has been upgraded from version 0.280206 to 0.280208.
Manifest files are now correctly embedded for those versions of VC++ which
-make use of them.
+make use of them. [perl #111782, #111798].
=item *
C<B::COP::stashlen> has been replaced with C<B::COP::stashoff>.
-C<B::COP::stashpv> now supports UTF8 package names and embedded nulls.
+C<B::COP::stashpv> now supports UTF8 package names and embedded NULs.
=item *
=item *
-L<ExtUtils::CBuilder> has been upgraded from version 0.280206 to 0.280208.
+L<DynaLoader> has been upgraded from version 1.14 to 1.15.
-It no longer fails when trying to embed manifests on Windows
-[perl #111782, #111798].
+This is due to a minor code change in the XS for the VMS implementation.
=item *
L<Pod::Html> has been upgraded from version 1.15_02 to 1.16.
-The option C<--libpods> has been re-instated. It is deprecated, and its use
+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.
=item *
=back
-=head2 Removed Modules and Pragmata
-
-=over 4
-
-=item *
-
-XXX
-
-=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
-
-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.
-
=head3 L<perlfaq>
=over 4
=head1 Diagnostics
-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.
-
-[ Within each section, list entries as a =item entry that links to perldiag,
- e.g.
-
- =item *
-
- L<Invalid version object|perldiag/"Invalid version object">
-]
-
-=head2 New Diagnostics
-
-XXX Newly added diagnostic messages go here
-
-=head3 New Errors
-
-=over 4
-
-=item *
-
-XXX L<message|perldiag/"message">
-
-=back
-
-=head3 New Warnings
-
-=over 4
-
-=item *
-
-XXX L<message|perldiag/"message">
-
-=back
-
-=head2 Changes to Existing Diagnostics
-
-XXX Changes (i.e. rewording) of diagnostic messages go here
-
-=over 4
-
-=item *
-
-XXX Describe change here
-
-=back
-
=head2 Removals of Diagnostics
=over 4
The "Not a format reference" error has been removed, as the only case in
which it could be triggered was a bug.
-=back
-
-=head1 Utility Changes
-
-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>.
-
-[ 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. ]
-
-=head3 L<XXX>
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=head1 Configuration and Compilation
-
-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.
-
-[ List changes as a =item entry ].
-
-=over 4
-
-=item *
-
-XXX
-
-=back
-
-=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 summarising, although the bugs
-that they represent may be covered elsewhere.
-
-[ List each test improvement as a =item entry ]
-
-=over 4
-
=item *
-XXX
+The "Unable to create sub named %s" error has been removed for the same
+reason.
=back
=head1 Platform Support
-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. ]
-
-=head2 New Platforms
-
-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.
-
-=over 4
-
-=item XXX-some-platform
-
-XXX
-
-=back
-
-=head2 Discontinued Platforms
-
-XXX List any platforms that this version of perl no longer compiles on.
-
-=over 4
-
-=item XXX-some-platform
-
-XXX
-
-=back
-
=head2 Platform-Specific Notes
-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.
+XXX note fails on win2k and vms
=over 4
=head1 Internal Changes
-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.
-
-[ List each change as a =item entry ]
-
=over 4
=item *
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 regexp plugin modules.
+should be initialised to NULL by other regex plugin modules.
=item *
=head1 Selected Bug Fixes
-XXX Important bug fixes in the core language are summarised here.
-Bug fixes in files in F<ext/> and F<lib/> are best summarised in
-L</Modules and Pragmata>.
-
-[ List each fix as a =item entry ]
-
=over 4
=item *
=item *
-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 $r pattern is
+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 $r are reused rather than being recompiled,
+compiled code-blocks within C<$r> are reused rather than being recompiled,
and C<use re 'eval'> isn't needed any more:
my $r = qr/abc(?{....})def/;
=item *
The "Can't find an opnumber" message that C<prototype> produces when passed
-a string like "CORE::nonexistent_keyword" is now passes UTF8 and embedded
-nulls through unchanged [perl #97478].
+a string like "CORE::nonexistent_keyword" now passes UTF8 and embedded
+NULs through unchanged [perl #97478].
=item *
=item *
-Under threaded perls, a run-time code block in a regular expression could
+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].
=item *
Unary negation no longer treats a string as a number if the string happened
-to be used as a number some time. So, if $x contains the string "dogs",
+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.
=item *
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
-matchs as if it had been written as C<qr/87/>, with a message that the
+matches as if it had been written as C<qr/87/>, with a message that the
sequence C<"\8"> is unrecognized.
=item *
inside a BEGIN block. It still does not work properly, but it no longer
crashes [perl #111610].
-=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, unless
-they were specific to a particular platform (see below).
-
-This is a list of some significant unfixed bugs, which are regressions
-from either 5.XXX.XXX or 5.XXX.XXX.
-
-[ List each fix as a =item entry ]
-
-=over 4
-
=item *
-XXX
+C<\&{''}> (with the empty string) now autovivifies a stub like any other
+sub name, and no longer produces the "Unable to create sub" error
+[perl #94476].
=back
-=head1 Obituary
-
-XXX If any significant core contributor has died, we've added a short obituary
-here.
-
=head1 Acknowledgements
XXX Generate this with:
https://perl5.git.perl.org / perl5.git / blobdiff