1=encoding utf8 2 3=head1 NAME 4 5perl5361delta - what is new for perl v5.36.1 6 7=head1 DESCRIPTION 8 9This document describes differences between the 5.36.0 release and the 5.36.1 10release. 11 12If you are upgrading from an earlier release such as 5.35.0, first read 13L<perl5360delta>, which describes differences between 5.35.0 and 5.36.0. 14 15=head1 Incompatible Changes 16 17There are no changes intentionally incompatible with 5.36.0. If any exist, 18they are bugs, and we request that you submit a report. See 19L</Reporting Bugs> below. 20 21=head1 Modules and Pragmata 22 23=head2 Updated Modules and Pragmata 24 25=over 4 26 27=item * 28 29L<Module::CoreList> has been upgraded from version 5.20220520 to 5.20230423. 30 31=back 32 33=head1 Configuration and Compilation 34 35=over 4 36 37=item * 38 39C<Configure> probed for the return type of malloc() and free() by testing 40whether declarations for those functions produced a function type mismatch with 41the implementation. On Solaris, with a C++ compiler, this check always failed, 42since Solaris instead imports malloc() and free() from C<std::> with C<using> 43for C++ builds. Since the return types of malloc() and free() are well defined 44by the C standard, skip probing for them. C<Configure> command-line arguments 45and hints can still override these type in the unlikely case that is needed. 46[L<GH #20806|https://github.com/Perl/perl5/issues/20806>] 47 48=back 49 50=head1 Testing 51 52Tests were added and changed to reflect the other additions and changes in this 53release. 54 55=head1 Selected Bug Fixes 56 57=over 4 58 59=item * 60 61An eval() as the last statement in a regex code block could trigger an 62interpreter panic; e.g. 63 64 /(?{ ...; eval {....}; })/ 65 66[L<GH #19680|https://github.com/Perl/perl5/issues/19680>] 67 68=item * 69 70An C<eval EXPR> referring to a lexical sub defined in grandparent scope no 71longer produces an assertion failures. 72[L<GH #19857|https://github.com/Perl/perl5/issues/19857>] 73 74=item * 75 76Writing to a magic variables associated with the selected output handle, C<$^>, 77C<$~>, C<$=>, C<$-> and C<$%>, no longer crashes perl if the IO object has been 78cleared from the selected output handle. 79[L<GH #20733|https://github.com/Perl/perl5/issues/20733>] 80 81=back 82 83=head1 Acknowledgements 84 85Perl 5.36.1 represents approximately 11 months of development since Perl 5.36.0 86and contains approximately 5,500 lines of changes across 62 files from 24 87authors. 88 89Excluding auto-generated files, documentation and release tools, there were 90approximately 1,600 lines of changes to 23 .pm, .t, .c and .h files. 91 92Perl continues to flourish into its fourth decade thanks to a vibrant community 93of users and developers. The following people are known to have contributed 94the improvements that became Perl 5.36.1: 95 96Andreas König, Bram, Chris 'BinGOs' Williams, Craig A. Berry, Dagfinn Ilmari 97Mannsåker, David Mitchell, Elvin Aslanov, Florian Weimer, Graham Knop, Hugo 98van der Sanden, Karen Etheridge, Karl Williamson, Leon Timmermans, Matthew 99Horsfall, Max Maischein, Neil Bowers, Nicolas R, Renee Baecker, Ricardo Signes, 100Richard Leach, Steve Hay, Todd Rinaldo, Tony Cook, Yves Orton. 101 102The list above is almost certainly incomplete as it is automatically generated 103from version control history. In particular, it does not include the names of 104the (very much appreciated) contributors who reported issues to the Perl bug 105tracker. 106 107Many of the changes included in this version originated in the CPAN modules 108included in Perl's core. We're grateful to the entire CPAN community for 109helping Perl to flourish. 110 111For a more complete list of all of Perl's historical contributors, please see 112the F<AUTHORS> file in the Perl source distribution. 113 114=head1 Reporting Bugs 115 116If you find what you think is a bug, you might check the perl bug database at 117L<https://github.com/Perl/perl5/issues>. There may also be information at 118L<http://www.perl.org/>, the Perl Home Page. 119 120If you believe you have an unreported bug, please open an issue at 121L<https://github.com/Perl/perl5/issues>. Be sure to trim your bug down to a 122tiny but sufficient test case. 123 124If the bug you are reporting has security implications which make it 125inappropriate to send to a public issue tracker, then see 126L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION> for details of how to 127report the issue. 128 129=head1 Give Thanks 130 131If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you 132can do so by running the C<perlthanks> program: 133 134 perlthanks 135 136This will send an email to the Perl 5 Porters list with your show of thanks. 137 138=head1 SEE ALSO 139 140The F<Changes> file for an explanation of how to view exhaustive details on 141what changed. 142 143The F<INSTALL> file for how to build Perl. 144 145The F<README> file for general stuff. 146 147The F<Artistic> and F<Copying> files for copyright information. 148 149=cut 150