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<perlfaq> has been upgraded from version 5.20201107 to 5.20210411.
25 - Added entry to faq4 for equivalent to ruby #{}, python fstring
29 L<ExtUtils::MakeMaker> has been upgraded from version 7.60 to 7.62
31 - Now using shellwords in ExtUtils::Liblist::Kid::_unix_os2_ext
35 L<NEXT> has been upgraded from version 0.67 to 0.68
37 - This aligns NEXT with changes already shipped with Perl as well as improving the test suite.
41 L<ExtUtils::ParseXS> has been upgraded from version 3.42 to 3.43
43 - Emphasize SvPVbyte and SvPVutf8 over SvPV in docs. Also includes minor output changes to clarify failure conditions.
53 L<perlguts> now explains in greater detail the need to consult SvUTF8
54 when calling SvPV (or variants). A new "How do I pass a Perl string to a C
55 library?" section in the same document discusses when to use which style of
56 macro to read an SV's string value.
58 L<perlapi>, L<perlguts>, L<perlxs>, and L<perlxstut> now prefer SvPVbyte
63 References to B<Pumpking> have been replaced with a more accurate term or B<Steering Council> where appropriate.
67 L<perldiag> now documents additional examples of "not imported" warnings.
71 B<The Perl Steering Council> is now the fallback contact for security issues.
75 Simplify the split() documentation by removing the join()s from the examples (#18676)
77 Remove join() from split() examples as it confuses the concepts
79 split() is a very basic function, and the documentation should be
80 simple for novinces. The split() documentation contains a lot of join()
81 in the examples which only serve to muddle the concepts. This replaces
82 the join() in the example with output in comments.
88 The following additions or changes have been made to diagnostic output,
89 including warnings and fatal error messages. For the complete list of
90 diagnostic messages, see L<perldiag>.
92 =head2 New Diagnostics
100 L<Wide character in setenv key (encoding to utf8)|perldiag/"Wide character in %s">
102 Attempts to put wide characters into environment variable keys via C<%ENV> now
103 provoke this warning.
107 =head1 Configuration and Compilation
113 Prevented incpath to spill into libpth
117 =item - Use realpath if available.
119 =item - This might catch more duplicate paths.
121 =item - Only include real existing paths.
123 =item - Filter inc paths out of libpth.
129 =head1 Platform Support
131 =head2 Platform-Specific Notes
137 Reading non-ASCII characters from the console when its codepage was set to
138 65001 (UTF-8) was broken due to a bug in Windows. A workaround for this
139 problem has been implemented.
140 [L<GH #18701|https://github.com/Perl/perl5/issues/18701>]
144 =head1 Internal Changes
150 Corrected handling of double and long double parameters for perl's
151 implementation of formatted output for C<-Dusequadmath> builds.
153 This applies to PerlIO_printf(), croak(), warn(), sv_catpvf() and
156 Previously in C<quadmath> builds, code like:
158 PerlIO_printf(PerlIO_stderr(), "%g", somedouble);
162 PerlIO_printf(PerlIO_stderr(), "%Lg", somelongdouble);
164 would erroneously throw an exception "panic: quadmath invalid format
165 ...", since the code added for quadmath builds assumed C<NV>s were the
166 only floating point format passed into these functions.
168 This code would also process the standard C long double specifier C<L>
169 as if it expected an C<NV> (C<__float128> for quadmath builds),
170 resulting in undefined behaviour.
172 These functions now correctly accept doubles, long doubles and NVs.
176 Previously the right operand of bitwise shift operators (shift amount)
177 was implicitly cast from IV to int, but it might lead wrong results
178 if IV does not fit in int.
180 And also, shifting INT_MIN bits used to yield the shiftee unchanged
181 (treated as 0-bit shift instead of negative shift).
185 =head1 Selected Bug Fixes
191 Setting %ENV now properly handles upgraded strings in the key. Previously
192 Perl sent the SV's internal PV directly to the OS; now it will handle keys
193 as it has handled values since 5.18: attempt to downgrade the string first;
194 if that fails then warn and use the utf8 form.
198 =head1 Acknowledgements
200 Perl 5.33.9 represents approximately 4 weeks of development since Perl
201 5.33.8 and contains approximately 3,900 lines of changes across 190 files
204 Excluding auto-generated files, documentation and release tools, there were
205 approximately 780 lines of changes to 82 .pm, .t, .c and .h files.
207 Perl continues to flourish into its fourth decade thanks to a vibrant
208 community of users and developers. The following people are known to have
209 contributed the improvements that became Perl 5.33.9:
211 Dan Book, Dominic Hamon, E. Choroba, Ed J, Felipe Gasper, H.Merijn Brand,
212 Hugo van der Sanden, James E Keenan, John Lightsey, Karen Etheridge, Karl
213 Williamson, Marc Reisner, Max Maischein, Nicolas R., Paul Evans, Ricardo
214 Signes, Richard Leach, Scott Baker, TAKAI Kousuke, Todd Rinaldo, Tomasz
215 Konojacki, Tony Cook, Михаил Козачков.
217 The list above is almost certainly incomplete as it is automatically
218 generated from version control history. In particular, it does not include
219 the names of the (very much appreciated) contributors who reported issues to
220 the Perl bug tracker.
222 Many of the changes included in this version originated in the CPAN modules
223 included in Perl's core. We're grateful to the entire CPAN community for
224 helping Perl to flourish.
226 For a more complete list of all of Perl's historical contributors, please
227 see the F<AUTHORS> file in the Perl source distribution.
229 =head1 Reporting Bugs
231 If you find what you think is a bug, you might check the perl bug database
232 at L<https://github.com/Perl/perl5/issues>. There may also be information at
233 L<http://www.perl.org/>, the Perl Home Page.
235 If you believe you have an unreported bug, please open an issue at
236 L<https://github.com/Perl/perl5/issues>. Be sure to trim your bug down to a
237 tiny but sufficient test case.
239 If the bug you are reporting has security implications which make it
240 inappropriate to send to a public issue tracker, then see
241 L<perlsec/SECURITY VULNERABILITY CONTACT INFORMATION>
242 for details of how to report the issue.
246 If you wish to thank the Perl 5 Porters for the work we had done in Perl 5,
247 you can do so by running the C<perlthanks> program:
251 This will send an email to the Perl 5 Porters list with your show of thanks.
255 The F<Changes> file for an explanation of how to view exhaustive details on
258 The F<INSTALL> file for how to build Perl.
260 The F<README> file for general stuff.
262 The F<Artistic> and F<Copying> files for copyright information.