PERL5163DELTA(1perl)

πŸ“¦
version 5.44.0 Β· 2 versions
, in arch rolling

✨ perl5163delta β€” what's new for perl v5.16.3 ✨

okay bestie, welcome to the <pink>perl5163delta</pink> page from the Perl Programmers Reference Guide πŸ’– this is your little group chat briefing on what changed.


🌸 DESCRIPTION 🌸

So like, this doc spills all the tea on the differences between the 5.16.2 release and the 5.16.3 release. πŸ’…

And if you're upgrading from an even earlier release, like 5.16.1? bestie you gotta read perl5162delta first, because that one covers the glow-up from 5.16.1 to 5.16.2. no skipping, iykyk πŸ¦‹


πŸ‘‘ Core Enhancements πŸ‘‘

No changes since 5.16.0. literally nothing, she's stable and thriving πŸ’€βœ¨


πŸ”₯ Security πŸ”₯

okay so THIS release contains one major security fix and a number of minor ones. the minor ones are mainly in there so the test suite passes cleanly with the clang compiler's address sanitizer facility. not dramatic, just tidy 🧚

πŸ’€ CVE-2013-1667: memory exhaustion with arbitrary hash keys

So here's the deal β€” with a carefully crafted set of hash keys (think, like, arguments on a URL πŸ‘€), it is possible to cause a hash to consume a large amount of memory and CPU, and thus possibly to achieve a Denial-of-Service. genuinely rude behaviour fr fr.

This problem has been fixed. πŸŽ€

πŸ’€ wrap-around with IO on long strings

Reading or writing strings greater than 2**31 bytes in size could segfault due to integer wraparound. yikes on bikes. 😭

This problem has been fixed. 🫢

πŸ’€ memory leak in Encode

The UTF-8 encoding implementation in Encode.xs had a memory leak πŸ’§ which has been fixed. slay.


🌈 Incompatible Changes 🌈

There are no changes intentionally incompatible with 5.16.0. and if any exist? those are bugs and reports are welcome, bestie, we want the receipts πŸ“¬


πŸ¦‹ Deprecations πŸ¦‹

There have been no deprecations since 5.16.0. nothing got cancelled, periodt. πŸ’œ


πŸŽ€ Modules and Pragmata πŸŽ€

⭐ Updated Modules and Pragmata

  • Encode has been upgraded from version 2.44 to version 2.44_01.
  • Module::CoreList has been upgraded from version 2.76 to version 2.76_02.
  • XS::APItest has been upgraded from version 0.38 to version 0.39.

look at them go, little version bumps, iconic ✨


πŸ™ˆ Known Problems πŸ™ˆ

None. clean. flawless. main character energy πŸ’…


πŸ’– Acknowledgements πŸ’–

Perl 5.16.3 represents approximately 4 months of development since Perl 5.16.2 and contains approximately 870 lines of changes across 39 files from 7 authors. that's a whole group project that actually got finished, obsessed 😭

Perl continues to flourish into its third decade thanks to a vibrant community of users and developers πŸ‘‘ The following people are known to have contributed the improvements that became Perl 5.16.3:

Andy Dougherty, Chris 'BinGOs' Williams, Dave Rolsky, David Mitchell, Michael Schroeder, Ricardo Signes, Yves Orton.

ngl the list above is almost certainly incomplete, because it is automatically generated from version control history. in particular, it does not include the names of the (very much appreciated 🫢) contributors who reported issues to the Perl bug tracker.

For a more complete list of all of Perl's historical contributors, please see the AUTHORS file in the Perl source distribution. go give them their flowers 🌸


πŸ“¬ Reporting Bugs πŸ“¬

If you find what you think is a bug, you might check the articles recently posted to the comp.lang.perl.misc newsgroup and the perl bug database at http://rt.perl.org/perlbug/ . There may also be information at http://www.perl.org/ , the Perl Home Page. πŸ¦‹

If you believe you have an unreported bug, please run the perlbug program included with your release. Be sure to trim your bug down to a tiny but sufficient test case πŸ” Your bug report, along with the output of perl -V, will be sent off to perlbug@perl.org to be analysed by the Perl porting team. send it, bestie πŸ’Œ

If the bug you are reporting has security implications, which make it inappropriate to send to a publicly archived mailing list, then please send it to perl5-security-report@perl.org. This points to a closed subscription unarchived mailing list, which includes all the core committers, who will be able to help assess the impact of issues, figure out a resolution, and help co-ordinate the release of patches to mitigate or fix the problem across all platforms on which Perl is supported. Please only use this address for security issues in the Perl core, not for modules independently distributed on CPAN. πŸ” very serious, very private, no group chats on this one.


🌟 SEE ALSO 🌟

The Changes file for an explanation of how to view exhaustive details on what changed. πŸ“

The INSTALL file for how to build Perl. πŸ”¨

The README file for general stuff. πŸ“–

The Artistic and Copying files for copyright information. ©️


and that's the whole tea, bestie πŸ“ this was perl v5.44.0, dated 2026-10-17, signed off by PERL5163DELTA(1perl) β€” mwah, go forth and upgrade responsibly πŸ’…βœ¨πŸ’–

πŸ“¦ where this page comes from
  • arch rolling: perl 5.44.0-1 Β· Artistic-1.0-Perl AND GPL-1.0-or-later
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms