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