[ 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.9
+perldelta - what is new for perl v5.31.2
=head1 DESCRIPTION
-This document describes differences between the 5.29.8 release and the 5.29.9
+This document describes differences between the 5.31.1 release and the 5.31.2
release.
-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.
+If you are upgrading from an earlier release such as 5.31.0, first read
+L<perl5311delta>, which describes differences between 5.31.0 and 5.31.1.
=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 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]).
-
-=head2 Any set of digits in the Common script are legal in a script run
-of another script
-
-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]
-
-All digits in a run still have to come from the same set of ten digits.
-
=head1 Deprecations
XXX Any deprecated features, syntax, modules etc. should be listed here.
=item *
-L<perl5db.pl> has been upgraded from version 1.54 to 1.55.
-
-Debugging threaded code no longer deadlocks in C<DB::sub> nor
-C<DB::lsub>.
-
- =item *
-
- L<Devel::PPPort> has been upgraded from version 3.44 to 3.45.
-
-=item *
-
-L<PerlIO::encoding> has been upgraded from version 0.26 to 0.27.
+L<XXX> has been upgraded from version A.xx to B.yy.
-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.
+If there was something important to note about this change, include that here.
=back
=item *
-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{}>.
+C<\N{} here is restricted to one character> is now emitted in the same
+circumstances where previously C<\N{} in inverted character class or as
+a range end-point is restricted to one character> was.
-=item *
-
-Within the scope of the experimental feature C<use re 'strict'>,
-specifying C<\x{}> without anything between the braces now yields the
-fatal error message "Empty \x{}". 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{}>. It is legal, though not wise
-to have an empty C<\x> outside of C<re 'strict'>; it silently generates
-a NUL character.
+This is due to new circumstances having been added in perl v5.30 that
+weren't covered by the earlier wording.
=back
=item *
-XXX
+The C<ECHO> macro is now defined. This is used in a C<dtrace> rule
+that was originally changed for FreeBSD, and the FreeBSD make
+apparently predefines it. The Solaris make does not predefine C<ECHO>
+which broke this rule on Solaris. [perl #134218]
+
+=item *
+
+Bison versions 3.1 through 3.4 are now supported.
=back
=over 4
-=item XXX-some-platform
+=item Linux
-XXX
+C<cc> will be used to populate C<plibpth> if C<cc> is C<clang>. [perl
+#134189]
+
+=item VMS
+
+C<-Duse64bitint> is now the default on VMS.
=back
=item *
-Added C<newSVsv_nomg()> to copy a SV without processing get magic on
-the source. [perl #132964]
+The PERL_DESTRUCT_LEVEL environment variable was formerly only honored on
+perl binaries built with DEBUGGING support. It is now checked on all perl
+builds. Its normal use is to force perl to individually free every block
+of memory which it has allocated before exiting, which is useful when
+using automated leak detection tools such as valgrind.
+
+=item *
+
+The API eval_sv() now accepts a C<G_RETHROW> flag. If this flag is
+set and an exception is thrown while compiling or executing the
+supplied code, it will be rethrown, and eval_sv() will not return.
+[perl #134177]
+
+=item *
+
+As part of the fix for [perl #2754] perl_parse() now returns non-zero
+if exit(0) is called in a C<BEGIN>, C<UNITCHECK> or C<CHECK> block.
=back
=item *
-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]
+Parsing incomplete hex or binary literals was changed in 5.31.1 to
+treat such a literal as just the 0, leaving the following C<x> or C<b>
+to be parsed as part of the next token. This could lead to some
+silent changes in behaviour, so now incomplete hex or binary literals
+produce a fatal error. [perl #134125]
+
+=item *
+
+eval_pv()'s I<croak_on_error> flag will now throw even if the
+exception is a false overloaded value. [perl #134177]
=item *
-See L</Any set of digits in the Common script are legal in a script run
-of another script>.
+C<INIT> blocks and the program itself are no longer run if exit(0) is
+called within a C<BEGIN>, C<UNITCHECK> or C<CHECK> block. [perl
+#2754]
+
+=item *
+
+C<<< open my $fh, ">>+", undef >>> now opens the temporary file in
+append mode - writes will seek to the end of file before writing.
+[perl #134221]
=back
=item *
-XXX
+The VC++ 6.0 build on Windows is currently broken.
+
+=item *
+
+Tests 9-11 in F<t/op/blocks.t> currently fail on Windows.
+[perl #134295]
=back
XXX Generate this with:
- perl Porting/acknowledgements.pl v5.29.8..HEAD
+ perl Porting/acknowledgements.pl v5.31.1..HEAD
=head1 Reporting Bugs