[ 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.23.6
+perldelta - what is new for perl v5.23.9
=head1 DESCRIPTION
-This document describes differences between the 5.23.5 release and the 5.23.6
+This document describes differences between the 5.23.8 release and the 5.23.9
release.
-If you are upgrading from an earlier release such as 5.23.4, first read
-L<perl5235delta>, which describes differences between 5.23.4 and 5.23.5.
+If you are upgrading from an earlier release such as 5.23.7, first read
+L<perl5238delta>, which describes differences between 5.23.7 and 5.23.8.
=head1 Notice
=head1 Incompatible Changes
-=head2 Some regular expression patterns that had runtime errors now
-don't compile at all
+XXX For a release on a stable branch, this section aspires to be:
-This should have been in the perldelta for 5.23.4, but was omitted.
+ 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.
-Almost all Unicode properties using the C<\p{}> and C<\P{}> regular
-expression pattern constructs are now checked for validity at pattern
-compilation time, and invalid ones will cause the program to not
-compile. In earlier releases, this check was often deferred until run
-time. Whenever an error check is moved from run- to compile time,
-erroneous code is caught 100% of the time, whereas before it would only
-get caught if and when the offending portion actually gets executed,
-which for unreachable code might be never.
+[ List each incompatible change as a =head2 entry ]
=head1 Deprecations
[ List each other deprecation as a =head2 entry ]
-=head2 Using code points above the platform's C<IV_MAX> is now
-deprecated
-
-Unicode defines code points in the range C<0..0x10FFFF>. Some standards
-at one time defined them up to 2**31 - 1, but Perl has allowed them to
-be as high as anything that will fit in a word on the platform being
-used. However, use of those above the platform's C<IV_MAX> is broken in
-some constructs, notably C<tr///>, regular expression patterns involving
-quantifiers, and in some arithmetic and comparison operations, such as
-being the upper limit of a loop. Now the use of such code points raises
-a deprecation warning, unless that warning category is turned off.
-C<IV_MAX> is typically 2**31 -1 on 32-bit platforms, and 2**63-1 on
-64-bit ones.
-
=head1 Performance Enhancements
XXX Changes which enhance performance without changing behaviour go here.
=item *
-L<DynaLoader> has been upgraded from version 1.36 to 1.37.
-
-Fixed an else nesting issue in dynamic loading support for OS/390 (and
-similar systems) that was introduced in 1.36.
+L<XXX> has been upgraded from version A.xx to B.yy.
=item *
-L<utf8> has been upgraded from 1.17 to 1.18.
-
-Partly reverted a micro-optimization to F<lib/utf_heavy.pl> that
-caused self-recursion when it was loaded with C<${^ENCODING}> set.
-[perl #126593]
+L<Module::CoreList> has been upgraded from version 5.20160121 to
+5.20160221.
=back
=item *
-L<message|perldiag/"Invalid number '%s' for -C option.">
-
-(F) You supplied a number to the -C option that either has extra leading
-zeroes or overflows perl's unsigned integer representation.
-
+XXX L<message|perldiag/"message">
=back
=item *
-F<make_ext.pl> is no longer inappropriately silent. This was caused
-by an operator precedence error introduced in 5.23.4.
+XXX
=back
=over 4
-=item EBCDIC platforms, such as z/OS
+=item Win32
-UTF-EBCDIC is like UTF-8, but for EBCDIC platforms. It now has been
-extended so that it can represent code points up to 2 ** 64 - 1 on
-platforms with 64-bit words. This brings it into parity with UTF-8.
-This enhancement requires an incompatible change to the representation
-of code points in the range 2 ** 30 to 2 ** 31 -1 (the latter was the
-previous maximum representable code point). This means that a file that
-contains one of these code points, written out with previous versions of
-perl cannot be read in, without conversion, by a perl containing this
-change. We do not believe any such files are in existence, but if you
-do have one, submit a ticket at L<mailto:perlbug@perl.org>, and we will
-write a conversion script for you.
+Building a 64-bit perl with a 64-bit GCC but a 32-bit gmake would
+result in an invalid C<$Config{archname}> for the resulting perl.
+[perl #127584]
=back
=item *
-C</...\G/> no longer crashes on utf8 strings. When C<\G> is a fixed number
-of characters from the start of the regex, perl needs to count back that
-many characters from the current C<pos()> position and start matching from
-there. However, it was counting back bytes rather than characters, which
-could lead to panics on utf8 strings.
-
-=item *
-
-In some cases operators that return integers would return negative
-integers as large positive integers. [perl #126635]
+It now works properly to specify a user-defined property, such as
-=item *
+ qr/\p{mypkg1::IsMyProperty}/i
-The pipe() operator would assert for DEBUGGING builds instead of
-producing the correct error message. The condition asserted on is
-detected and reported on correctly without the assertions, so the
-assertions were removed. [perl #126480]
+with C</i> caseless matching, an explicit package name, and
+I<IsMyProperty> not defined at the time of the pattern compilation.
=item *
-In some cases, failing to parse a here-doc would attempt to use freed
-memory. This was caused by a pointer not being restored correctly.
-[perl #126443]
+Perl's memcpy(), memmove(), memset() and memcmp() fallbacks are now
+more compatible with the originals. [perl #127619]
=back
XXX Generate this with:
- perl Porting/acknowledgements.pl v5.23.5..HEAD
+ perl Porting/acknowledgements.pl v5.23.8..HEAD
=head1 Reporting Bugs
https://perl5.git.perl.org / perl5.git / blobdiff