[ 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.25.10
+perldelta - what is new for perl v5.27.2
=head1 DESCRIPTION
-This document describes differences between the 5.25.9 release and the 5.25.10
+This document describes differences between the 5.27.1 release and the 5.27.2
release.
-If you are upgrading from an earlier release such as 5.25.8, first read
-L<perl5259delta>, which describes differences between 5.25.8 and 5.25.9.
+If you are upgrading from an earlier release such as 5.27.0, first read
+L<perl5271delta>, which describes differences between 5.27.0 and 5.27.1.
=head1 Notice
[ List each enhancement as a =head2 entry ]
+=head2 Unicode 10.0 is supported
+
+A list of changes is at
+L<http://www.unicode.org/versions/Unicode10.0.0>.
+
=head1 Security
XXX Any security-related notices go here. In particular, any security
=head2 Changes to Existing Documentation
+We have attempted to update the documentation to reflect the changes
+listed in this document. If you find any we have missed, send email
+to L<perlbug@perl.org|mailto:perlbug@perl.org>.
+
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.
+Additionally, the following selected changes have been made:
+
=head3 L<XXX>
=over 4
=item *
-Use of unassigned code point or non-standalone grapheme for a delimiter will be a fatal error starting in Perl 5.30
-
-This was changed to drop a leading C<v> in C<v5.30>, so it uses the same
-style as other deprecation messages.
+XXX Describe change here
=back
Changes to existing files in F<t/> aren't worth summarizing, although the bugs
that they represent may be covered elsewhere.
+XXX If there were no significant test changes, say this:
+
+Tests were added and changed to reflect the other additions and changes
+in this release.
+
+XXX If instead there were significant changes, say this:
+
+Tests were added and changed to reflect the other additions and
+changes in this release. Furthermore, these significant changes were
+made:
+
[ List each test improvement as a =item entry ]
=over 4
=item *
-The C<op_class()> API function has been added. This is like the existing
-C<OP_CLASS()> macro, but can more accurately determine what struct an op
-has been allocated as. For example C<OP_CLASS()> might return
-C<OA_BASEOP_OR_UNOP> indicating that ops of this type are usually
-allocated as an C<OP> or C<UNOP>; while <op_class()> will return
-C<OPclass_BASEOP> or C<OPclass_UNOP> as appropriate.
-
-=item *
-
-The output format of the C<op_dump()> function (as used by C<perl -Dx>)
-has changed: it now displays an "ASCII-art" tree structure, and shows more
-low-level details about each op, such as its address and class.
+XXX
=back
=item *
-Attempting to use the deprecated variable C<$#> as the object in an
-indirect object method call could cause a heap use after free or
-buffer overflow. [perl #129274]
+List assignment (C<aassign>) could in some rare cases allocate an
+entry on the mortal stack and leave the entry uninitialized. [perl
+#131570]
=item *
-When checking for an indirect object method call in some rare cases
-the parser could reallocate the line buffer but then continue to use
-pointers to the old buffer. [perl #129190]
+Attempting to apply an attribute to an C<our> variable where a
+function of that name already exists could result in a NULL pointer
+being supplied where an SV was expected, crashing perl. [perl
+#131597]
=back
L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
for details of how to report the issue.
+=head1 Give Thanks
+
+If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
+you can do so by running the C<perlthanks> program:
+
+ perlthanks
+
+This will send an email to the Perl 5 Porters list with your show of thanks.
+
=head1 SEE ALSO
The F<Changes> file for an explanation of how to view exhaustive details on
https://perl5.git.perl.org / perl5.git / blobdiff