[ 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.29.1
+perldelta - what is new for perl v5.29.9
=head1 DESCRIPTION
-This document describes differences between the 5.29.0 release and the 5.29.1
+This document describes differences between the 5.29.8 release and the 5.29.9
release.
-If you are upgrading from an earlier release such as 5.28.0, first read
-L<perl5290delta>, which describes differences between 5.28.0 and 5.29.0.
+If you are upgrading from an earlier release such as 5.29.7, first read
+L<perl5298delta>, which describes differences between 5.29.7 and 5.29.8.
=head1 Notice
[ List each enhancement as a =head2 entry ]
+=head2 Wildcards in Unicode property value specifications are now
+partially supported
+
+You can now do something like this in a regular expression pattern
+
+ qr! \p{nv= /(?x) \A [0-5] \z / }!
+
+which matches all Unicode code points which have numeric value is
+between 0 and 5 inclusive.
+
+This marks another step in implementing the regular expression features
+the Unicode Consortium suggests.
+
+Most properties are supported, with the remainder planned for 5.32.
+Details are in L<perlunicode/Wildcards in Property Values>.
+
+=head2 qr'\N{name}' is now supported
+
+Previously it was an error to evaluate a named character C<\N{...}>
+within a single quoted regular expression pattern (whose evaluation is
+deferred from the normal place). This restriction is now removed.
+
+=head2 Unicode 12.0 is supported
+
+For details, see L<https://www.unicode.org/versions/Unicode12.0.0/>.
+
+Because of a change in Unicode release cycles, Perl jumps from Unicode
+10.0 in Perl 5.28 to Unicode 12.0 in Perl 5.30.
+
+=head2 It is now possible to compile perl to always use thread-safe
+locale operations.
+
+Previously, these calls were only used when the perl was compiled to be
+multi-threaded. To always enable them, add
+
+ -Accflags='-DUSE_THREAD_SAFE_LOCALE'
+
+to your F<Configure> flags.
+
+
=head1 Security
XXX Any security-related notices go here. In particular, any security
[ List each security issue as a =head2 entry ]
+=head2 Variable length lookbehind in regular expression pattern matching
+is now experimentally supported
+
+Using a lookbehind assertion (like C<(?<=foo)> or C<(?<!bar)> previously
+would generate an error and refuse to compile. Now it compiles (if the
+maximum lookbehind is at most 255 characters), but raises a warning in
+the new C<experimental::vlb> warnings category. This is to caution you
+that the precise behavior is subject to change based on feedback from
+use in the field.
+
+See L<perlre/(?<=pattern)> and L<perlre/(?<!pattern)>.
+
=head1 Incompatible Changes
XXX For a release on a stable branch, this section aspires to be:
[ List each incompatible change as a =head2 entry ]
-=head2 Delimiters must now be graphemes
+=head2 C<pack()> no longer can return malformed UTF-8
+
+It croaks if it would otherwise return a UTF-8 string that contains
+malformed UTF-8. This protects agains potential security threats. This
+is considered a bug fix as well ([perl #131642]).
-See L<perldeprecation/Use of unassigned code point or non-standalone grapheme for a delimiter.>
+=head2 Any set of digits in the Common script are legal in a script run
+of another script
-=head2 Some formerly deprecated uses of an unescaped left brace C<"{">
-in regular expression patterns are now illegal
+There are several sets of digits in the Common script. C<[0-9]> is the
+most familiar. But there are also C<[\x{FF10}-\x{FF19}]> (FULLWIDTH
+DIGIT ZERO - FULLWIDTH DIGIT NINE), and several sets for use in
+mathematical notation, such as the MATHEMATICAL DOUBLE-STRUCK DIGITs.
+Any of these sets should be able to appear in script runs of, say,
+Greek. But the design of 5.30 overlooked all but the ASCII digits
+C<[0-9]>, so the design was flawed. This has been fixed, so is both a
+bug fix and an incompatibility. [perl #133547]
-But to avoid breaking code unnecessarily, most instances that issued a
-deprecation warning, remain legal and now have a non-deprecation warning
-raised. See L<perldeprecation/Unescaped left braces in regular
-expressions>.
+All digits in a run still have to come from the same set of ten digits.
=head1 Deprecations
=item *
-Translating from UTF-8 into the code point it represents now is done via
-a deterministic finite automaton, speeding it up. As a typical example,
-C<ord("\x7fff")> now requires 12% fewer instructions than before.
-The performance of checking that a sequence of bytes is valid UTF-8 is
-similarly improved, again by using a dfa.
+XXX
=back
=item *
-L<XXX> has been upgraded from version A.xx to B.yy.
+L<perl5db.pl> has been upgraded from version 1.54 to 1.55.
-If there was something important to note about this change, include that here.
+Debugging threaded code no longer deadlocks in C<DB::sub> nor
+C<DB::lsub>.
+
+=item *
+
+L<PerlIO::encoding> has been upgraded from version 0.26 to 0.27.
+
+Warnings enabled by setting the C<WARN_ON_ERR> flag in
+C<$PerlIO::encoding::fallback> are now only produced if warnings are
+enabled with C<use warnings "utf8";> or setting C<$^W>.
+
+=item *
+
+L<threads::shared> has been upgraded from version 1.59 to 1.60.
+
+Added support for extra tracing of locking, this requires a
+C<-DDEBUGGING> and extra compilation flags.
=back
=item *
-XXX Describe change here
+Specifying C<\o{}> without anything between the braces now yields the
+fatal error message "Empty \o{}". Previously it was "Number with no
+digits". This means the same wording is used for this kind of error as
+with similar constructs such as C<\p{}>.
=back
=item *
-XXX
+Added C<newSVsv_nomg()> to copy a SV without processing get magic on
+the source. [perl #132964]
=back
=item *
-XXX
+C<pack()> no longer can return malformed UTF-8. It croaks if it would
+otherwise return a UTF-8 string that contains malformed UTF-8. This
+protects agains potential security threats. [perl #131642]
+
+=item *
+
+See L</Any set of digits in the Common script are legal in a script run
+of another script>.
=back
XXX Generate this with:
- perl Porting/acknowledgements.pl v5.27.11..HEAD
+ perl Porting/acknowledgements.pl v5.29.8..HEAD
=head1 Reporting Bugs
If you find what you think is a bug, you might check the perl bug database
-at L<https://rt.perl.org/> . There may also be information at
-L<http://www.perl.org/> , the Perl Home Page.
+at L<https://rt.perl.org/>. There may also be information at
+L<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
https://perl5.git.perl.org / perl5.git / blobdiff