5 perldelta - what is new for perl v5.33.9
9 This document describes differences between the 5.33.8 release and the 5.33.9
12 If you are upgrading from an earlier release such as 5.33.7, first read
13 L<perl5338delta>, which describes differences between 5.33.7 and 5.33.8.
15 =head1 Modules and Pragmata
17 =head2 Updated Modules and Pragmata
23 L<Data::Dumper> has been upgraded from version 2.177 to 2.178.
27 L<ExtUtils::MakeMaker> has been upgraded from version 7.60 to 7.62.
31 L<ExtUtils::ParseXS> has been upgraded from version 3.42 to 3.43.
35 L<ExtUtils::Typemaps> has been upgraded from version 3.38 to 3.43.
39 L<feature> has been upgraded from version 1.63 to 1.64.
43 L<Module::CoreList> has been upgraded from version 5.20210320 to 5.20210420.
47 L<NEXT> has been upgraded from version 0.67_01 to 0.68.
51 L<perlfaq> has been upgraded from version 5.20201107 to 5.20210411.
55 L<XS::APItest> has been upgraded from version 1.15 to 1.16.
65 L<perlguts> now explains in greater detail the need to consult SvUTF8
66 when calling SvPV (or variants). A new "How do I pass a Perl string to a C
67 library?" section in the same document discusses when to use which style of
68 macro to read an SV's string value.
70 L<perlapi>, L<perlguts>, L<perlxs>, and L<perlxstut> now prefer SvPVbyte
75 References to B<Pumpking> have been replaced with a more accurate term or B<Steering Council> where appropriate.
79 L<perldiag> now documents additional examples of "not imported" warnings.
83 B<The Perl Steering Council> is now the fallback contact for security issues.
87 Simplify the split() documentation by removing the join()s from the examples (#18676)
89 Remove join() from split() examples as it confuses the concepts
91 split() is a very basic function, and the documentation should be
92 simple for novinces. The split() documentation contains a lot of join()
93 in the examples which only serve to muddle the concepts. This replaces
94 the join() in the example with output in comments.
100 The following additions or changes have been made to diagnostic output,
101 including warnings and fatal error messages. For the complete list of
102 diagnostic messages, see L<perldiag>.
104 =head2 New Diagnostics
112 L<Wide character in setenv key (encoding to utf8)|perldiag/"Wide character in %s">
114 Attempts to put wide characters into environment variable keys via C<%ENV> now
115 provoke this warning.
119 =head1 Configuration and Compilation
125 Prevented incpath to spill into libpth
129 =item - Use realpath if available.
131 =item - This might catch more duplicate paths.
133 =item - Only include real existing paths.
135 =item - Filter inc paths out of libpth.
141 =head1 Platform Support
143 =head2 Platform-Specific Notes
149 Reading non-ASCII characters from the console when its codepage was set to
150 65001 (UTF-8) was broken due to a bug in Windows. A workaround for this
151 problem has been implemented.
152 [L<GH #18701|https://github.com/Perl/perl5/issues/18701>]
156 =head1 Internal Changes
162 Corrected handling of double and long double parameters for perl's
163 implementation of formatted output for C<-Dusequadmath> builds.
165 This applies to PerlIO_printf(), croak(), warn(), sv_catpvf() and
168 Previously in C<quadmath> builds, code like:
170 PerlIO_printf(PerlIO_stderr(), "%g", somedouble);
174 PerlIO_printf(PerlIO_stderr(), "%Lg", somelongdouble);
176 would erroneously throw an exception "panic: quadmath invalid format
177 ...", since the code added for quadmath builds assumed C<NV>s were the
178 only floating point format passed into these functions.
180 This code would also process the standard C long double specifier C<L>
181 as if it expected an C<NV> (C<__float128> for quadmath builds),
182 resulting in undefined behaviour.
184 These functions now correctly accept doubles, long doubles and NVs.
188 Previously the right operand of bitwise shift operators (shift amount)
189 was implicitly cast from IV to int, but it might lead wrong results
190 if IV does not fit in int.
192 And also, shifting INT_MIN bits used to yield the shiftee unchanged
193 (treated as 0-bit shift instead of negative shift).
197 =head1 Selected Bug Fixes
203 Setting %ENV now properly handles upgraded strings in the key. Previously
204 Perl sent the SV's internal PV directly to the OS; now it will handle keys
205 as it has handled values since 5.18: attempt to downgrade the string first;
206 if that fails then warn and use the utf8 form.
210 =head1 Acknowledgements
212 Perl 5.33.9 represents approximately 4 weeks of development since Perl
213 5.33.8 and contains approximately 3,900 lines of changes across 190 files
216 Excluding auto-generated files, documentation and release tools, there were
217 approximately 780 lines of changes to 82 .pm, .t, .c and .h files.
219 Perl continues to flourish into its fourth decade thanks to a vibrant
220 community of users and developers. The following people are known to have
221 contributed the improvements that became Perl 5.33.9:
223 Dan Book, Dominic Hamon, E. Choroba, Ed J, Felipe Gasper, H.Merijn Brand,
224 Hugo van der Sanden, James E Keenan, John Lightsey, Karen Etheridge, Karl
225 Williamson, Marc Reisner, Max Maischein, Nicolas R., Paul Evans, Ricardo
226 Signes, Richard Leach, Scott Baker, TAKAI Kousuke, Todd Rinaldo, Tomasz
227 Konojacki, Tony Cook, Михаил Козачков.
229 The list above is almost certainly incomplete as it is automatically
230 generated from version control history. In particular, it does not include
231 the names of the (very much appreciated) contributors who reported issues to
232 the Perl bug tracker.
234 Many of the changes included in this version originated in the CPAN modules
235 included in Perl's core. We're grateful to the entire CPAN community for
236 helping Perl to flourish.
238 For a more complete list of all of Perl's historical contributors, please
239 see the F<AUTHORS> file in the Perl source distribution.
241 =head1 Reporting Bugs
243 If you find what you think is a bug, you might check the perl bug database
244 at L<https://github.com/Perl/perl5/issues>. There may also be information at
245 L<http://www.perl.org/>, the Perl Home Page.
247 If you believe you have an unreported bug, please open an issue at
248 L<https://github.com/Perl/perl5/issues>. Be sure to trim your bug down to a
249 tiny but sufficient test case.
251 If the bug you are reporting has security implications which make it
252 inappropriate to send to a public issue tracker, then see
253 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
254 for details of how to report the issue.
258 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
259 you can do so by running the C<perlthanks> program:
263 This will send an email to the Perl 5 Porters list with your show of thanks.
267 The F<Changes> file for an explanation of how to view exhaustive details on
270 The F<INSTALL> file for how to build Perl.
272 The F<README> file for general stuff.
274 The F<Artistic> and F<Copying> files for copyright information.