{ "content": [ { "type": "text", "text": "# perl5300delta (man)\n\n## NAME\n\nperl5300delta - what is new for perl v5.30.0\n\n## DESCRIPTION\n\nThis document describes differences between the 5.28.0 release and the 5.30.0 release.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **Notice** (23 subsections)\n- **Deprecations** (5 subsections)\n- **Documentation** (1 subsections)\n- **Diagnostics** (4 subsections)\n- **Testing** (4 subsections)\n- **Acknowledgements** (2 subsections)\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "perl5300delta", "section": "", "mode": "man", "summary": "perl5300delta - what is new for perl v5.30.0", "synopsis": null, "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 5, "subsections": [] }, { "name": "Notice", "lines": 3, "subsections": [ { "name": "Core Enhancements", "lines": 1 }, { "name": "Limited variable length lookbehind in regular expression pattern matching is now experimentally", "lines": 1 }, { "name": "supported", "lines": 8 }, { "name": "The upper limit \"n\" specifiable in a regular expression quantifier of the form \"{m,n}\" has been", "lines": 1 }, { "name": "doubled to 65534", "lines": 4 }, { "name": "Unicode 12.1 is supported", "lines": 15 }, { "name": "Wildcards in Unicode property value specifications are now partially supported", "lines": 13 }, { "name": "qr'\\N{name}' is now supported", "lines": 4 }, { "name": "Turkic UTF-8 locales are now seamlessly supported", "lines": 6 }, { "name": "It is now possible to compile perl to always use thread-safe locale operations.", "lines": 7 }, { "name": "Eliminate opASSIGN macro usage from core", "lines": 2 }, { "name": "\"-Drv\" now means something on \"-DDEBUGGING\" builds", "lines": 3 }, { "name": "Incompatible Changes", "lines": 1 }, { "name": "Assigning non-zero to $[ is fatal", "lines": 3 }, { "name": "Delimiters must now be graphemes", "lines": 3 }, { "name": "Some formerly deprecated uses of an unescaped left brace \"{\" in regular expression patterns are", "lines": 1 }, { "name": "now illegal", "lines": 4 }, { "name": "Previously deprecated sysread()/syswrite() on :utf8 handles is now fatal", "lines": 14 }, { "name": "my() in false conditional prohibited", "lines": 9 }, { "name": "Fatalize unqualified use of dump()", "lines": 5 }, { "name": "Remove File::Glob::glob()", "lines": 5 }, { "name": "\"pack()\" no longer can return malformed UTF-8", "lines": 4 }, { "name": "Any set of digits in the Common script are legal in a script run of another script", "lines": 14 } ] }, { "name": "Deprecations", "lines": 1, "subsections": [ { "name": "In XS code, use of various macros dealing with UTF-8.", "lines": 4 }, { "name": "Performance Enhancements", "lines": 30 }, { "name": "Modules and Pragmata", "lines": 1 }, { "name": "Updated Modules and Pragmata", "lines": 202 }, { "name": "Removed Modules and Pragmata", "lines": 19 } ] }, { "name": "Documentation", "lines": 1, "subsections": [ { "name": "Changes to Existing Documentation", "lines": 50 } ] }, { "name": "Diagnostics", "lines": 3, "subsections": [ { "name": "Changes to Existing Diagnostics", "lines": 30 }, { "name": "Utility Changes", "lines": 1 }, { "name": "xsubpp", "lines": 4 }, { "name": "Configuration and Compilation", "lines": 13 } ] }, { "name": "Testing", "lines": 19, "subsections": [ { "name": "Platform Support", "lines": 1 }, { "name": "Platform-Specific Notes", "lines": 56 }, { "name": "Internal Changes", "lines": 24 }, { "name": "Selected Bug Fixes", "lines": 171 } ] }, { "name": "Acknowledgements", "lines": 33, "subsections": [ { "name": "Reporting Bugs", "lines": 13 }, { "name": "Give Thanks", "lines": 7 } ] }, { "name": "SEE ALSO", "lines": 11, "subsections": [] } ], "sections": { "NAME": { "content": "perl5300delta - what is new for perl v5.30.0\n", "subsections": [] }, "DESCRIPTION": { "content": "This document describes differences between the 5.28.0 release and the 5.30.0 release.\n\nIf you are upgrading from an earlier release such as 5.26.0, first read perl5280delta, which\ndescribes differences between 5.26.0 and 5.28.0.\n", "subsections": [] }, "Notice": { "content": "svutf8(downgrade|decode) are no longer marked as experimental. [GH #16822]\n.\n", "subsections": [ { "name": "Core Enhancements", "content": "" }, { "name": "Limited variable length lookbehind in regular expression pattern matching is now experimentally", "content": "" }, { "name": "supported", "content": "Using a lookbehind assertion (like \"(?<=foo?)\" or \"(? for\n11.0; for 12.0; and\n for 12.1. (Unicode 12.1 differs from 12.0\nonly in the addition of a single character, that for the new Japanese era name.)\n\nThe WordBreak property, as in past Perl releases, remains tailored to behave more in line\nwith expectations of Perl users. This means that sequential runs of horizontal white space\ncharacters are not broken apart, but kept as a single run. Unicode 11 changed from past\nversions to be more in line with Perl, but it left several white space characters as causing\nbreaks: TAB, NO BREAK SPACE, and FIGURE SPACE (U+2007). We have decided to continue to use\nthe previous Perl tailoring with regards to these.\n" }, { "name": "Wildcards in Unicode property value specifications are now partially supported", "content": "You can now do something like this in a regular expression pattern\n\nqr! \\p{nv= /(?x) \\A [0-5] \\z / }!\n\nwhich matches all Unicode code points whose numeric value is between 0 and 5 inclusive. So,\nit could match the Thai or Bengali digits whose numeric values are 0, 1, 2, 3, 4, or 5.\n\nThis marks another step in implementing the regular expression features the Unicode\nConsortium suggests.\n\nMost properties are supported, with the remainder planned for 5.32. Details are in\n\"Wildcards in Property Values\" in perlunicode.\n" }, { "name": "qr'\\N{name}' is now supported", "content": "Previously it was an error to evaluate a named character \"\\N{...}\" within a single quoted\nregular expression pattern (whose evaluation is deferred from the normal place). This\nrestriction is now removed.\n" }, { "name": "Turkic UTF-8 locales are now seamlessly supported", "content": "Turkic languages have different casing rules than other languages for the characters \"i\" and\n\"I\". The uppercase of \"i\" is LATIN CAPITAL LETTER I WITH DOT ABOVE (U+0130); and the\nlowercase of \"I\" is LATIN SMALL LETTER DOTLESS I (U+0131). Unicode furnishes alternate\ncasing rules for use with Turkic languages. Previously, Perl ignored these, but now, it uses\nthem when it detects that it is operating under a Turkic UTF-8 locale.\n" }, { "name": "It is now possible to compile perl to always use thread-safe locale operations.", "content": "Previously, these calls were only used when the perl was compiled to be multi-threaded. To\nalways enable them, add\n\n-Accflags='-DUSETHREADSAFELOCALE'\n\nto your Configure flags.\n" }, { "name": "Eliminate opASSIGN macro usage from core", "content": "This macro is still defined but no longer used in core\n" }, { "name": "\"-Drv\" now means something on \"-DDEBUGGING\" builds", "content": "Now, adding the verbose flag (\"-Dv\") to the \"-Dr\" flag turns on all possible regular\nexpression debugging.\n" }, { "name": "Incompatible Changes", "content": "" }, { "name": "Assigning non-zero to $[ is fatal", "content": "Setting $[ to a non-zero value has been deprecated since Perl 5.12 and now throws a fatal\nerror. See \"Assigning non-zero to $[ is fatal\" in perldeprecation.\n" }, { "name": "Delimiters must now be graphemes", "content": "See \"Use of unassigned code point or non-standalone grapheme for a delimiter.\" in\nperldeprecation\n" }, { "name": "Some formerly deprecated uses of an unescaped left brace \"{\" in regular expression patterns are", "content": "" }, { "name": "now illegal", "content": "But to avoid breaking code unnecessarily, most instances that issued a deprecation warning,\nremain legal and now have a non-deprecation warning raised. See \"Unescaped left braces in\nregular expressions\" in perldeprecation.\n" }, { "name": "Previously deprecated sysread()/syswrite() on :utf8 handles is now fatal", "content": "Calling sysread(), syswrite(), send() or recv() on a \":utf8\" handle, whether applied\nexplicitly or implicitly, is now fatal. This was deprecated in perl 5.24.\n\nThere were two problems with calling these functions on \":utf8\" handles:\n\n• All four functions only paid attention to the \":utf8\" flag. Other layers were completely\nignored, so a handle with \":encoding(UTF-16LE)\" layer would be treated as UTF-8. Other\nlayers, such as compression are completely ignored with or without the \":utf8\" flag.\n\n• sysread() and recv() would read from the handle, skipping any validation by the layers,\nand do no validation of their own. This could lead to invalidly encoded perl scalars.\n\n[GH #14839] .\n" }, { "name": "my() in false conditional prohibited", "content": "Declarations such as \"my $x if 0\" are no longer permitted.\n\n[GH #16702] .\n\nFatalize $* and $#\nThese special variables, long deprecated, now throw exceptions when used.\n\n[GH #16718] .\n" }, { "name": "Fatalize unqualified use of dump()", "content": "The \"dump()\" function, long discouraged, may no longer be used unless it is fully qualified,\ni.e., \"CORE::dump()\".\n\n[GH #16719] .\n" }, { "name": "Remove File::Glob::glob()", "content": "The \"File::Glob::glob()\" function, long deprecated, has been removed and now throws an\nexception which advises use of \"File::Glob::bsdglob()\" instead.\n\n[GH #16721] .\n" }, { "name": "\"pack()\" no longer can return malformed UTF-8", "content": "It croaks if it would otherwise return a UTF-8 string that contains malformed UTF-8. This\nprotects against potential security threats. This is considered a bug fix as well. [GH\n#16035] .\n" }, { "name": "Any set of digits in the Common script are legal in a script run of another script", "content": "There are several sets of digits in the Common script. \"[0-9]\" is the most familiar. But\nthere are also \"[\\x{FF10}-\\x{FF19}]\" (FULLWIDTH DIGIT ZERO - FULLWIDTH DIGIT NINE), and\nseveral sets for use in mathematical notation, such as the MATHEMATICAL DOUBLE-STRUCK DIGITs.\nAny of these sets should be able to appear in script runs of, say, Greek. But the design of\n5.30 overlooked all but the ASCII digits \"[0-9]\", so the design was flawed. This has been\nfixed, so is both a bug fix and an incompatibility. [GH #16704]\n.\n\nAll digits in a run still have to come from the same set of ten digits.\n\nJSON::PP enables allownonref by default\nAs JSON::XS 4.0 changed its policy and enabled allownonref by default, JSON::PP also enabled\nallownonref by default.\n" } ] }, "Deprecations": { "content": "", "subsections": [ { "name": "In XS code, use of various macros dealing with UTF-8.", "content": "This deprecation was scheduled to become fatal in 5.30, but has been delayed to 5.32 due to\nproblems that showed up with some CPAN modules. For details of what's affected, see\nperldeprecation.\n" }, { "name": "Performance Enhancements", "content": "• Translating from UTF-8 into the code point it represents now is done via a deterministic\nfinite automaton, speeding it up. As a typical example, \"ord(\"\\x7fff\")\" now requires 12%\nfewer instructions than before. The performance of checking that a sequence of bytes is\nvalid UTF-8 is similarly improved, again by using a DFA.\n\n• Eliminate recursion from finalizeop(). [GH #11866]\n.\n\n• A handful of small optimizations related to character folding and character classes in\nregular expressions.\n\n• Optimization of \"IV\" to \"UV\" conversions. [GH #16761]\n.\n\n• Speed up of the integer stringification algorithm by processing two digits at a time\ninstead of one. [GH #16769] .\n\n• Improvements based on LGTM analysis and recommendation.\n(). [GH #16765]\n. [GH #16773]\n.\n\n• Code optimizations in regcomp.c, regcomp.h, regexec.c.\n\n• Regular expression pattern matching of things like \"qr/[^a]/\" is significantly sped up,\nwhere a is any ASCII character. Other classes can get this speed up, but which ones is\ncomplicated and depends on the underlying bit patterns of those characters, so differs\nbetween ASCII and EBCDIC platforms, but all case pairs, like \"qr/[Gg]/\" are included, as\nis \"[^01]\".\n" }, { "name": "Modules and Pragmata", "content": "" }, { "name": "Updated Modules and Pragmata", "content": "• Archive::Tar has been upgraded from version 2.30 to 2.32.\n\n• B has been upgraded from version 1.74 to 1.76.\n\n• B::Concise has been upgraded from version 1.003 to 1.004.\n\n• B::Deparse has been upgraded from version 1.48 to 1.49.\n\n• bignum has been upgraded from version 0.49 to 0.51.\n\n• bytes has been upgraded from version 1.06 to 1.07.\n\n• Carp has been upgraded from version 1.38 to 1.50\n\n• Compress::Raw::Bzip2 has been upgraded from version 2.074 to 2.084.\n\n• Compress::Raw::Zlib has been upgraded from version 2.076 to 2.084.\n\n• Config::Extensions has been upgraded from version 0.02 to 0.03.\n\n• Config::Perl::V. has been upgraded from version 0.29 to 0.32. This was due to a new\nconfiguration variable that has influence on binary compatibility:\n\"USETHREADSAFELOCALE\".\n\n• CPAN has been upgraded from version 2.20 to 2.22.\n\n• Data::Dumper has been upgraded from version 2.170 to 2.174\n\nData::Dumper now avoids leaking when \"croak\"ing.\n\n• DBFile has been upgraded from version 1.840 to 1.843.\n\n• deprecate has been upgraded from version 0.03 to 0.04.\n\n• Devel::Peek has been upgraded from version 1.27 to 1.28.\n\n• Devel::PPPort has been upgraded from version 3.40 to 3.52.\n\n• Digest::SHA has been upgraded from version 6.01 to 6.02.\n\n• Encode has been upgraded from version 2.97 to 3.01.\n\n• Errno has been upgraded from version 1.29 to 1.30.\n\n• experimental has been upgraded from version 0.019 to 0.020.\n\n• ExtUtils::CBuilder has been upgraded from version 0.280230 to 0.280231.\n\n• ExtUtils::Manifest has been upgraded from version 1.70 to 1.72.\n\n• ExtUtils::Miniperl has been upgraded from version 1.08 to 1.09.\n\n• ExtUtils::ParseXS has been upgraded from version 3.39 to 3.40. \"OUTLIST\" parameters are\nno longer incorrectly included in the automatically generated function prototype. [GH\n#16746] .\n\n• feature has been upgraded from version 1.52 to 1.54.\n\n• File::Copy has been upgraded from version 2.33 to 2.34.\n\n• File::Find has been upgraded from version 1.34 to 1.36.\n\n$File::Find::dontusenlink now defaults to 1 on all platforms. [GH #16759]\n.\n\nVariables $IsWin32 and $IsVMS are being initialized.\n\n• File::Glob has been upgraded from version 1.31 to 1.32.\n\n• File::Path has been upgraded from version 2.15 to 2.16.\n\n• File::Spec has been upgraded from version 3.74 to 3.78.\n\nSilence Cwd warning on Android builds if \"targetsh\" is not defined.\n\n• File::Temp has been upgraded from version 0.2304 to 0.2309.\n\n• Filter::Util::Call has been upgraded from version 1.58 to 1.59.\n\n• GDBMFile has been upgraded from version 1.17 to 1.18.\n\n• HTTP::Tiny has been upgraded from version 0.070 to 0.076.\n\n• I18N::Langinfo has been upgraded from version 0.17 to 0.18.\n\n• IO has been upgraded from version 1.39 to 1.40.\n\n• IO-Compress has been upgraded from version 2.074 to 2.084.\n\nAdds support for \"IO::Uncompress::Zstd\" and \"IO::Uncompress::UnLzip\".\n\nThe \"BinModeIn\" and \"BinModeOut\" options are now no-ops. ALL files will be read/written\nin binmode.\n\n• IPC::Cmd has been upgraded from version 1.00 to 1.02.\n\n• JSON::PP has been upgraded from version 2.97001 to 4.02.\n\nJSON::PP as JSON::XS 4.0 enables \"allownonref\" by default.\n\n• lib has been upgraded from version 0.64 to 0.65.\n\n• Locale::Codes has been upgraded from version 3.56 to 3.57.\n\n• Math::BigInt has been upgraded from version 1.999811 to 1.999816.\n\n\"bnok()\" now supports the full Kronenburg extension. [cpan #95628]\n.\n\n• Math::BigInt::FastCalc has been upgraded from version 0.5006 to 0.5008.\n\n• Math::BigRat has been upgraded from version 0.2613 to 0.2614.\n\n• Module::CoreList has been upgraded from version 5.20180622 to 5.20190520.\n\nChanges to B::Opprivate and Config\n\n• Module::Load has been upgraded from version 0.32 to 0.34.\n\n• Module::Metadata has been upgraded from version 1.000033 to 1.000036.\n\nProperly clean up temporary directories after testing.\n\n• NDBMFile has been upgraded from version 1.14 to 1.15.\n\n• Net::Ping has been upgraded from version 2.62 to 2.71.\n\n• ODBMFile has been upgraded from version 1.15 to 1.16.\n\n• PathTools has been upgraded from version 3.74 to 3.78.\n\n• parent has been upgraded from version 0.236 to 0.237.\n\n• perl5db.pl has been upgraded from version 1.54 to 1.55.\n\nDebugging threaded code no longer deadlocks in \"DB::sub\" nor \"DB::lsub\".\n\n• perlfaq has been upgraded from version 5.021011 to 5.20190126.\n\n• PerlIO::encoding has been upgraded from version 0.26 to 0.27.\n\nWarnings enabled by setting the \"WARNONERR\" flag in $PerlIO::encoding::fallback are now\nonly produced if warnings are enabled with \"use warnings \"utf8\";\" or setting $^W.\n\n• PerlIO::scalar has been upgraded from version 0.29 to 0.30.\n\n• podlators has been upgraded from version 4.10 to 4.11.\n\n• POSIX has been upgraded from version 1.84 to 1.88.\n\n• re has been upgraded from version 0.36 to 0.37.\n\n• SDBMFile has been upgraded from version 1.14 to 1.15.\n\n• sigtrap has been upgraded from version 1.08 to 1.09.\n\n• Storable has been upgraded from version 3.08 to 3.15.\n\nStorable no longer probes for recursion limits at build time. [GH #16780]\n and others.\n\nMetasploit exploit code was included to test for CVE-2015-1992 detection, this caused\nanti-virus detections on at least one AV suite. The exploit code has been removed and\nreplaced with a simple functional test. [GH #16778]\n\n\n• Test::Simple has been upgraded from version 1.302133 to 1.302162.\n\n• Thread::Queue has been upgraded from version 3.12 to 3.13.\n\n• threads::shared has been upgraded from version 1.58 to 1.60.\n\nAdded support for extra tracing of locking, this requires a \"-DDEBUGGING\" and extra\ncompilation flags.\n\n• Time::HiRes has been upgraded from version 1.9759 to 1.9760.\n\n• Time::Local has been upgraded from version 1.25 to 1.28.\n\n• Time::Piece has been upgraded from version 1.3204 to 1.33.\n\n• Unicode::Collate has been upgraded from version 1.25 to 1.27.\n\n• Unicode::UCD has been upgraded from version 0.70 to 0.72.\n\n• User::grent has been upgraded from version 1.02 to 1.03.\n\n• utf8 has been upgraded from version 1.21 to 1.22.\n\n• vars has been upgraded from version 1.04 to 1.05.\n\n\"vars.pm\" no longer disables non-vars strict when checking if strict vars is enabled.\n[GH #15851] .\n\n• version has been upgraded from version 0.9923 to 0.9924.\n\n• warnings has been upgraded from version 1.42 to 1.44.\n\n• XS::APItest has been upgraded from version 0.98 to 1.00.\n\n• XS::Typemap has been upgraded from version 0.16 to 0.17.\n" }, { "name": "Removed Modules and Pragmata", "content": "The following modules will be removed from the core distribution in a future release, and\nwill at that time need to be installed from CPAN. Distributions on CPAN which require these\nmodules will need to list them as prerequisites.\n\nThe core versions of these modules will now issue \"deprecated\"-category warnings to alert you\nto this fact. To silence these deprecation warnings, install the modules in question from\nCPAN.\n\nNote that these are (with rare exceptions) fine modules that you are encouraged to continue\nto use. Their disinclusion from core primarily hinges on their necessity to bootstrapping a\nfully functional, CPAN-capable Perl installation, not usually on concerns over their design.\n\n• B::Debug is no longer distributed with the core distribution. It continues to be\navailable on CPAN as \"B::Debug \".\n\n• Locale::Codes has been removed at the request of its author. It continues to be\navailable on CPAN as \"Locale::Codes \" [GH #16660]\n.\n" } ] }, "Documentation": { "content": "", "subsections": [ { "name": "Changes to Existing Documentation", "content": "We have attempted to update the documentation to reflect the changes listed in this document.\nIf you find any we have missed, send email to perlbug@perl.org .\n\nperlapi\n\n• \"AvFILL()\" was wrongly listed as deprecated. This has been corrected. [GH #16586]\n\n\nperlop\n\n• We no longer have null (empty line) here doc terminators, so perlop should not refer to\nthem.\n\n• The behaviour of \"tr\" when the delimiter is an apostrophe has been clarified. In\nparticular, hyphens aren't special, and \"\\x{}\" isn't interpolated. [GH #15853]\n\n\nperlreapi, perlvar\n\n• Improve docs for lastparen, lastcloseparen.\n\nperlfunc\n\n• The entry for \"-X\" in perlfunc has been clarified to indicate that symbolic links are\nfollowed for most tests.\n\n• Clarification of behaviour of \"reset EXPR\".\n\n• Try to clarify that \"ref(qr/xx/)\" returns \"Regexp\" rather than \"REGEXP\" and why. [GH\n#16801] .\n\nperlreref\n\n• Clarification of the syntax of /(?(cond)yes)/.\n\nperllocale\n\n• There are actually two slightly different types of UTF-8 locales: one for Turkic\nlanguages and one for everything else. Starting in Perl v5.30, Perl seamlessly handles\nboth types.\n\nperlrecharclass\n\n• Added a note for the ::xdigit:: character class.\n\nperlvar\n\n• More specific documentation of paragraph mode. [GH #16787]\n.\n" } ] }, "Diagnostics": { "content": "The following additions or changes have been made to diagnostic output, including warnings\nand fatal error messages. For the complete list of diagnostic messages, see perldiag.\n", "subsections": [ { "name": "Changes to Existing Diagnostics", "content": "• As noted under \"Incompatible Changes\" above, the deprecation warning \"Unescaped left\nbrace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in\nregex; marked by <-- HERE in m/%s/\" has been changed to the non-deprecation warning\n\"Unescaped left brace in regex is passed through in regex; marked by <-- HERE in m/%s/\".\n\n• Specifying \"\\o{}\" without anything between the braces now yields the fatal error message\n\"Empty \\o{}\". Previously it was \"Number with no digits\". This means the same wording\nis used for this kind of error as with similar constructs such as \"\\p{}\".\n\n• Within the scope of the experimental feature \"use re 'strict'\", specifying \"\\x{}\" without\nanything between the braces now yields the fatal error message \"Empty \\x{}\". Previously\nit was \"Number with no digits\". This means the same wording is used for this kind of\nerror as with similar constructs such as \"\\p{}\". It is legal, though not wise to have an\nempty \"\\x\" outside of \"re 'strict'\"; it silently generates a NUL character.\n\n• Type of arg %d to %s must be %s (not %s)\n\nAttempts to push, pop, etc on a hash or glob now produce this message rather than\ncomplaining that they no longer work on scalars. [GH #15774]\n.\n\n• Prototype not terminated\n\nThe file and line number is now reported for this error. [GH #16697]\n\n\n• Under \"-Dr\" (or \"use re 'Debug'\") the compiled regex engine program is displayed. It used\nto use two different spellings for infinity, \"INFINITY\", and \"INFTY\". It now uses the\nlatter exclusively, as that spelling has been around the longest.\n" }, { "name": "Utility Changes", "content": "" }, { "name": "xsubpp", "content": "• The generated prototype (with \"PROTOTYPES: ENABLE\") would include \"OUTLIST\" parameters,\nbut these aren't arguments to the perl function. This has been rectified. [GH #16746]\n.\n" }, { "name": "Configuration and Compilation", "content": "• Normally the thread-safe locale functions are used only on threaded builds. It is now\npossible to force their use on unthreaded builds on systems that have them available, by\nincluding the \"-Accflags='-DUSETHREADSAFELOCALE'\" option to Configure.\n\n• Improve detection of memrchr, strlcat, and strlcpy\n\n• Improve Configure detection of memmem(). [GH #16807]\n.\n\n• Multiple improvements and fixes for -DPERLGLOBALSTRUCT build option.\n\n• Fix -DPERLGLOBALSTRUCTPRIVATE build option.\n" } ] }, "Testing": { "content": "• t/lib/croak/op [GH #15774] .\n\nseparate error for \"push\", etc. on hash/glob.\n\n• t/op/svleak.t [GH #16749] .\n\nAdd test for \"goto &sub\" in overload leaking.\n\n• Split t/re/foldgrind.t into multiple test files.\n\n• Fix intermittent tests which failed due to race conditions which surface during parallel\ntesting. [GH #16795] .\n\n• Thoroughly test paragraph mode, using a new test file, t/io/paragraphmode.t. [GH\n#16787] .\n\n• Some tests in t/io/eintr.t caused the process to hang on pre-16 Darwin. These tests are\nskipped for those version of Darwin.\n", "subsections": [ { "name": "Platform Support", "content": "" }, { "name": "Platform-Specific Notes", "content": "HP-UX 11.11\nAn obscure problem in \"pack()\" when compiling with HP C-ANSI-C has been fixed by\ndisabling optimizations in pppack.c.\n\nMac OS X\nPerl's build and testing process on Mac OS X for \"-Duseshrplib\" builds is now compatible\nwith Mac OS X System Integrity Protection (SIP).\n\nSIP prevents binaries in /bin (and a few other places) being passed the\n\"DYLDLIBRARYPATH\" environment variable. For our purposes this prevents\n\"DYLDLIBRARYPATH\" from being passed to the shell, which prevents that variable being\npassed to the testing or build process, so running \"perl\" couldn't find libperl.dylib.\n\nTo work around that, the initial build of the perl executable expects to find\nlibperl.dylib in the build directory, and the library path is then adjusted during\ninstallation to point to the installed library.\n\n[GH #15057] .\n\nMinix3\nSome support for Minix3 has been re-added.\n\nCygwin\nCygwin doesn't make \"cuserid\" visible.\n\nWin32 Mingw\nC99 math functions are now available.\n\nWindows\n• The \"USECPLUSPLUS\" build option which has long been available in win32/Makefile (for\nnmake) and win32/makefile.mk (for dmake) is now also available in win32/GNUmakefile\n(for gmake).\n\n• The nmake makefile no longer defaults to Visual C++ 6.0 (a very old version which is\nunlikely to be widely used today). As a result, it is now a requirement to specify\nthe \"CCTYPE\" since there is no obvious choice of which modern version to default to\ninstead. Failure to specify \"CCTYPE\" will result in an error being output and the\nbuild will stop.\n\n(The dmake and gmake makefiles will automatically detect which compiler is being\nused, so do not require \"CCTYPE\" to be set. This feature has not yet been added to\nthe nmake makefile.)\n\n• \"sleep()\" with warnings enabled for a \"USEIMPSYS\" build no longer warns about the\nsleep timeout being too large. [GH #16631]\n.\n\n• Support for compiling perl on Windows using Microsoft Visual Studio 2019 (containing\nVisual C++ 14.2) has been added.\n\n• socket() now sets $! if the protocol, address family and socket type combination is\nnot found. [GH #16849] .\n\n• The Windows Server 2003 SP1 Platform SDK build, with its early x64 compiler and\ntools, was accidentally broken in Perl 5.27.9. This has now been fixed.\n" }, { "name": "Internal Changes", "content": "• The sizing pass has been eliminated from the regular expression compiler. An extra pass\nmay instead be needed in some cases to count the number of parenthetical capture groups.\n\n• A new function \"\"mystrtod\"\" in perlapi or its synonym, Strtod(), is now available with\nthe same signature as the libc strtod(). It provides strotod() equivalent behavior on\nall platforms, using the best available precision, depending on platform capabilities and\nConfigure options, while handling locale-related issues, such as if the radix character\nshould be a dot or comma.\n\n• Added \"newSVsvnomg()\" to copy a SV without processing get magic on the source. [GH\n#16461] .\n\n• It is now forbidden to malloc more than \"PTRDIFFTMAX\" bytes. Much code (including C\noptimizers) assumes that all data structures will not be larger than this, so this\ncatches such attempts before overflow happens.\n\n• Two new regnodes have been introduced \"EXACTONLY8\", and \"EXACTFUONLY8\". They're\nequivalent to \"EXACT\" and \"EXACTFU\", except that they contain a code point which requires\nUTF-8 to represent/match. Hence, if the target string isn't UTF-8, we know it can't\npossibly match, without needing to try.\n\n• \"printbytesforlocale()\" is now defined if \"DEBUGGING\", Prior, it didn't get defined\nunless \"LCCOLLATE\" was defined on the platform.\n" }, { "name": "Selected Bug Fixes", "content": "• Compilation under \"-DPERLMEMLOG\" and \"-DNOLOCALE\" have been fixed.\n\n• Perl 5.28 introduced an \"index()\" optimization when comparing to -1 (or indirectly, e.g.\n>= 0). When this optimization was triggered inside a \"when\" clause it caused a warning\n(\"Argument %s isn't numeric in smart match\"). This has now been fixed. [GH #16626]\n\n\n• The new in-place editing code no longer leaks directory handles. [GH #16602]\n.\n\n• Warnings produced from constant folding operations on overloaded values no longer produce\nspurious \"Use of uninitialized value\" warnings. [GH #16349]\n.\n\n• Fix for \"mutator not seen in (lex = ...) .= ...\" [GH #16655]\n.\n\n• \"pack \"u\", \"invalid uuencoding\"\" now properly NUL terminates the zero-length SV produced.\n[GH #16343] .\n\n• Improve the debugging output for calloc() calls with \"-Dm\". [GH #16653]\n.\n\n• Regexp script runs were failing to permit ASCII digits in some cases. [GH #16704]\n.\n\n• On Unix-like systems supporting a platform-specific technique for determining $^X, Perl\nfailed to fall back to the generic technique when the platform-specific one fails (for\nexample, a Linux system with /proc not mounted). This was a regression in Perl 5.28.0.\n[GH #16715] .\n\n• SDBMFile is now more robust with corrupt database files. The improvements do not make\nSDBM files suitable as an interchange format. [GH #16164]\n.\n\n• \"binmode($fh);\" or \"binmode($fh, ':raw');\" now properly removes the \":utf8\" flag from the\ndefault \":crlf\" I/O layer on Win32. [GH #16730]\n.\n\n• The experimental reference aliasing feature was misinterpreting array and hash slice\nassignment as being localised, e.g.\n\n\\(@a[3,5,7]) = \\(....);\n\nwas being interpreted as:\n\nlocal \\(@a[3,5,7]) = \\(....);\n\n[GH #16701] .\n\n• \"sort SUBNAME\" within an \"eval EXPR\" when \"EXPR\" was UTF-8 upgraded could panic if the\n\"SUBNAME\" was non-ASCII. [GH #16979] .\n\n• Correctly handle realloc() modifying \"errno\" on success so that the modification isn't\nvisible to the perl user, since realloc() is called implicitly by the interpreter. This\nmodification is permitted by the C standard, but has only been observed on FreeBSD\n13.0-CURRENT. [GH #16907] .\n\n• Perl now exposes POSIX \"getcwd\" as \"Internals::getcwd()\" if available. This is intended\nfor use by \"Cwd.pm\" during bootstrapping and may be removed or changed without notice.\nThis fixes some bootstrapping issues while building perl in a directory where some\nancestor directory isn't readable. [GH #16903]\n.\n\n• \"pack()\" no longer can return malformed UTF-8. It croaks if it would otherwise return a\nUTF-8 string that contains malformed UTF-8. This protects against potential security\nthreats. [GH #16035] .\n\n• See \"Any set of digits in the Common script are legal in a script run of another script\".\n\n• Regular expression matching no longer leaves stale UTF-8 length magic when updating $^R.\nThis could result in \"length($^R)\" returning an incorrect value.\n\n• Reduce recursion on ops [GH #11866] .\n\nThis can prevent stack overflow when processing extremely deep op trees.\n\n• Avoid leak in multiconcat with overloading. [GH #16823]\n.\n\n• The handling of user-defined \"\\p{}\" properties (see \"User-Defined Character Properties\"\nin perlunicode) has been rewritten to be in C (instead of Perl). This speeds things up,\nbut in the process several inconsistencies and bug fixes are made.\n\n1. A few error messages have minor wording changes. This is essentially because the new\nway is integrated into the regex error handling mechanism that marks the position in\nthe input at which the error occurred. That was not possible previously. The\nmessages now also contain additional back-trace-like information in case the error\noccurs deep in nested calls.\n\n2. A user-defined property is implemented as a perl subroutine with certain highly\nconstrained naming conventions. It was documented previously that the sub would be\nin the current package if the package was unspecified. This turned out not to be\ntrue in all cases, but now it is.\n\n3. All recursive calls are treated as infinite recursion. Previously they would cause\nthe interpreter to panic. Now, they cause the regex pattern to fail to compile.\n\n4. Similarly, any other error likely would lead to a panic; now to just the pattern\nfailing to compile.\n\n5. The old mechanism did not detect illegal ranges in the definition of the property.\nNow, the range max must not be smaller than the range min. Otherwise, the pattern\nfails to compile.\n\n6. The intention was to have each sub called only once during the lifetime of the\nprogram, so that a property's definition is immutable. This was relaxed so that it\ncould be called once for all /i compilations, and potentially a second time for\nnon-/i (the sub is passed a parameter indicating which). However, in practice there\nwere instances when this was broken, and multiple calls were possible. Those have\nbeen fixed. Now (besides the /i,non-/i cases) the only way a sub can be called\nmultiple times is if some component of it has not been defined yet. For example,\nsuppose we have sub IsA() whose definition is known at compile time, and it in turn\ncalls isB() whose definition is not yet known. isA() will be called each time a\npattern it appears in is compiled. If isA() also calls isC() and that definition is\nknown, isC() will be called just once.\n\n7. There were some races and very long hangs should one thread be compiling the same\nproperty as another simultaneously. These have now been fixed.\n\n• Fixed a failure to match properly.\n\nAn EXACTFish regnode has a finite length it can hold for the string being matched. If\nthat length is exceeded, a second node is used for the next segment of the string, for as\nmany regnodes as are needed. Care has to be taken where to break the string, in order to\ndeal multi-character folds in Unicode correctly. If we want to break a string at a place\nwhich could potentially be in the middle of a multi-character fold, we back off one (or\nmore) characters, leaving a shorter EXACTFish regnode. This backing off mechanism\ncontained an off-by-one error. [GH #16806] .\n\n• A bare \"eof\" call with no previous file handle now returns true. [GH #16786]\n\n\n• Failing to compile a format now aborts compilation. Like other errors in sub-parses this\ncould leave the parser in a strange state, possibly crashing perl if compilation\ncontinued. [GH #16169] \n\n• If an in-place edit is still in progress during global destruction and the process exit\ncode (as stored in $?) is zero, perl will now treat the in-place edit as successful,\nreplacing the input file with any output produced.\n\nThis allows code like:\n\nperl -i -ne 'print \"Foo\"; last'\n\nto replace the input file, while code like:\n\nperl -i -ne 'print \"Foo\"; die'\n\nwill not. Partly resolves [GH #16748] .\n\n• A regression in 5.28 caused the following code to fail\n\nclose(STDIN); open(CHILD, \"|wc -l\")'\n\nbecause the child's stdin would be closed on exec. This has now been fixed.\n\n• Fixed an issue where compiling a regexp containing both compile-time and run-time code\nblocks could lead to trying to compile something which is invalid syntax.\n\n• Fixed build failures with \"-DNOLOCALENUMERIC\" and \"-DNOLOCALECOLLATE\". [GH #16771]\n.\n\n• Prevent the tests in ext/B/t/strict.t from being skipped. [GH #16783]\n.\n\n• \"/di\" nodes ending or beginning in s are now \"EXACTF\". We do not want two \"EXACTFU\" to be\njoined together during optimization, and to form a \"ss\", \"sS\", \"Ss\" or \"SS\" sequence;\nthey are the only multi-character sequences which may match differently under \"/ui\" and\n\"/di\".\n" } ] }, "Acknowledgements": { "content": "Perl 5.30.0 represents approximately 11 months of development since Perl 5.28.0 and contains\napproximately 620,000 lines of changes across 1,300 files from 58 authors.\n\nExcluding auto-generated files, documentation and release tools, there were approximately\n510,000 lines of changes to 750 .pm, .t, .c and .h files.\n\nPerl continues to flourish into its fourth decade thanks to a vibrant community of users and\ndevelopers. The following people are known to have contributed the improvements that became\nPerl 5.30.0:\n\nAaron Crane, Abigail, Alberto Simões, Alexandr Savca, Andreas König, Andy Dougherty,\nAristotle Pagaltzis, Brian Greenfield, Chad Granum, Chris 'BinGOs' Williams, Craig A. Berry,\nDagfinn Ilmari Mannsåker, Dan Book, Dan Dedrick, Daniel Dragan, Dan Kogai, David Cantrell,\nDavid Mitchell, Dominic Hargreaves, E. Choroba, Ed J, Eugen Konkov, François Perrad, Graham\nKnop, Hauke D, H.Merijn Brand, Hugo van der Sanden, Jakub Wilk, James Clarke, James E Keenan,\nJerry D. Hedden, Jim Cromie, John SJ Anderson, Karen Etheridge, Karl Williamson, Leon\nTimmermans, Matthias Bethke, Nicholas Clark, Nicolas R., Niko Tyni, Pali, Petr Písař, Phil\nPearl (Lobbes), Richard Leach, Ryan Voots, Sawyer X, Shlomi Fish, Sisyphus, Slaven Rezic,\nSteve Hay, Sullivan Beck, Tina Müller, Tomasz Konojacki, Tom Wyant, Tony Cook, Unicode\nConsortium, Yves Orton, Zak B. Elep.\n\nThe list above is almost certainly incomplete as it is automatically generated from version\ncontrol history. In particular, it does not include the names of most of the (very much\nappreciated) contributors who reported issues to the Perl bug tracker. Noteworthy in this\nrelease were the large number of bug fixes made possible by Sergey Aleynikov's high quality\nperlbug reports for issues he discovered by fuzzing with AFL.\n\nMany of the changes included in this version originated in the CPAN modules included in\nPerl's core. We're grateful to the entire CPAN community for helping Perl to flourish.\n\nFor a more complete list of all of Perl's historical contributors, please see the AUTHORS\nfile in the Perl source distribution.\n", "subsections": [ { "name": "Reporting Bugs", "content": "If you find what you think is a bug, you might check the perl bug database at\n. There may also be information at , the Perl\nHome Page.\n\nIf you believe you have an unreported bug, please run the perlbug program included with your\nrelease. Be sure to trim your bug down to a tiny but sufficient test case. Your bug report,\nalong with the output of \"perl -V\", will be sent off to perlbug@perl.org to be analysed by\nthe Perl porting team.\n\nIf the bug you are reporting has security implications which make it inappropriate to send to\na publicly archived mailing list, then see \"SECURITY VULNERABILITY CONTACT INFORMATION\" in\nperlsec for details of how to report the issue.\n" }, { "name": "Give Thanks", "content": "If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by\nrunning the \"perlthanks\" program:\n\nperlthanks\n\nThis will send an email to the Perl 5 Porters list with your show of thanks.\n" } ] }, "SEE ALSO": { "content": "The Changes file for an explanation of how to view exhaustive details on what changed.\n\nThe INSTALL file for how to build Perl.\n\nThe README file for general stuff.\n\nThe Artistic and Copying files for copyright information.\n\n\n\nperl v5.34.0 2025-07-25 PERL5300DELTA(1)", "subsections": [] } } } }