[ 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.33.8
+perldelta - what is new for perl v5.35.3
=head1 DESCRIPTION
-This document describes differences between the 5.33.7 release and the 5.33.8
+This document describes differences between the 5.35.2 release and the 5.35.3
release.
-If you are upgrading from an earlier release such as 5.33.6, first read
-L<perl5337delta>, which describes differences between 5.33.6 and 5.33.7.
+If you are upgrading from an earlier release such as 5.35.1, first read
+L<perl5352delta>, which describes differences between 5.35.1 and 5.35.2.
=head1 Notice
significant internal changes for future core maintainers should be noted as
well.
-=over 4
-
-=item *
-
-A set of cop_hints_exists_{pv,pvn,pvs,sv} functions was added, to support checking
-for the existence of keys in the hints hash of a specific cop without needing to
-create a mortal copy of said value.
-
-=item *
-
-An aid has been added for using the C<DEBUG> macros when debugging XS or
-C code. The comments in F<perl.h> describe C<DEBUG_PRE_STMTS> and
-C<DEBUG_POST_STMTS>. which you can C<#define> to do things like save and
-restore C<errno>, in case the C<DEBUG> calls are interfering with that,
-or to display timestamps, or which thread it's coming from, or the
-location of the call, or whatever. You can make a quick hack to help
-you track something down without having to edit individual C<DEBUG>
-calls.
-
-=back
-
+[ List each change as an =item entry ]
=over 4
XXX Generate this with:
- perl Porting/acknowledgements.pl v5.33.7..HEAD
+ perl Porting/acknowledgements.pl v5.35.2..HEAD
=head1 Reporting Bugs