--- - branch: MAIN date: Sun Aug 11 10:14:18 UTC 2019 files: - new: '1.255' old: '1.254' path: pkgsrc/lang/perl5/Makefile pathrev: pkgsrc/lang/perl5/Makefile@1.255 type: modified - new: '1.37' old: '1.36' path: pkgsrc/lang/perl5/Makefile.common pathrev: pkgsrc/lang/perl5/Makefile.common@1.37 type: modified - new: '1.63' old: '1.62' path: pkgsrc/lang/perl5/buildlink3.mk pathrev: pkgsrc/lang/perl5/buildlink3.mk@1.63 type: modified - new: '1.158' old: '1.157' path: pkgsrc/lang/perl5/distinfo pathrev: pkgsrc/lang/perl5/distinfo@1.158 type: modified - new: '0' old: '1.1' path: pkgsrc/lang/perl5/files/cpan-DB_File-hints-bitrig.pl pathrev: pkgsrc/lang/perl5/files/cpan-DB_File-hints-bitrig.pl@0 type: deleted - new: '0' old: '1.1' path: pkgsrc/lang/perl5/files/cpan-DB_File-hints-minix.pl pathrev: pkgsrc/lang/perl5/files/cpan-DB_File-hints-minix.pl@0 type: deleted - new: '0' old: '1.1' path: pkgsrc/lang/perl5/files/cpan-DB_File-hints-netbsd.pl pathrev: pkgsrc/lang/perl5/files/cpan-DB_File-hints-netbsd.pl@0 type: deleted - new: '0' old: '1.1' path: pkgsrc/lang/perl5/files/cpan-DB_File-hints-openbsd.pl pathrev: pkgsrc/lang/perl5/files/cpan-DB_File-hints-openbsd.pl@0 type: deleted - new: '1.8' old: '1.7' path: pkgsrc/lang/perl5/patches/patch-Configure pathrev: pkgsrc/lang/perl5/patches/patch-Configure@1.8 type: modified - new: '1.9' old: '1.8' path: pkgsrc/lang/perl5/patches/patch-Makefile.SH pathrev: pkgsrc/lang/perl5/patches/patch-Makefile.SH@1.9 type: modified - new: '0' old: '1.2' path: pkgsrc/lang/perl5/patches/patch-dist_Storable_Makefile.PL pathrev: pkgsrc/lang/perl5/patches/patch-dist_Storable_Makefile.PL@0 type: deleted - new: '0' old: '1.1' path: pkgsrc/lang/perl5/patches/patch-t_io_fs.t pathrev: pkgsrc/lang/perl5/patches/patch-t_io_fs.t@0 type: deleted id: 20190811T101418Z.48dc1df632e958099d3addc4c14d31c2e9675192 log: | perl: updated to 5.30.0 what is new for perl v5.30.0 Core Enhancements Limited variable length lookbehind in regular expression pattern matching is now experimentally supported Using a lookbehind assertion (like "(?<=foo?)" or "(? for 11.0; for 12.0; and for 12.1. (Unicode 12.1 differs from 12.0 only in the addition of a single character, that for the new Japanese era name.) The Word_Break property, as in past Perl releases, remains tailored to behave more in line with expectations of Perl users. This means that sequential runs of horizontal white space characters are not broken apart, but kept as a single run. Unicode 11 changed from past versions to be more in line with Perl, but it left several white space characters as causing breaks: TAB, NO BREAK SPACE, and FIGURE SPACE (U+2007). We have decided to continue to use the previous Perl tailoring with regards to these. Wildcards in Unicode property value specifications are now partially supported You can now do something like this in a regular expression pattern qr! \p{nv= /(?x) \A [0-5] \z / }! which matches all Unicode code points whose numeric value is between 0 and 5 inclusive. So, it could match the Thai or Bengali digits whose numeric values are 0, 1, 2, 3, 4, or 5. This marks another step in implementing the regular expression features the Unicode Consortium suggests. Most properties are supported, with the remainder planned for 5.32. Details are in "Wildcards in Property Values" in perlunicode. qr'\N{name}' is now supported Previously it was an error to evaluate a named character "\N{...}" within a single quoted regular expression pattern (whose evaluation is deferred from the normal place). This restriction is now removed. Turkic UTF-8 locales are now seamlessly supported Turkic languages have different casing rules than other languages for the characters "i" and "I". The uppercase of "i" is LATIN CAPITAL LETTER I WITH DOT ABOVE (U+0130); and the lowercase of "I" is LATIN SMALL LETTER DOTLESS I (U+0131). Unicode furnishes alternate casing rules for use with Turkic languages. Previously, Perl ignored these, but now, it uses them when it detects that it is operating under a Turkic UTF-8 locale. It is now possible to compile perl to always use thread-safe locale operations. Previously, these calls were only used when the perl was compiled to be multi-threaded. To always enable them, add -Accflags='-DUSE_THREAD_SAFE_LOCALE' to your Configure flags. Eliminate opASSIGN macro usage from core This macro is still defined but no longer used in core "-Drv" now means something on "-DDEBUGGING" builds Now, adding the verbose flag ("-Dv") to the "-Dr" flag turns on all possible regular expression debugging. Incompatible Changes Assigning non-zero to $[ is fatal Setting $[ to a non-zero value has been deprecated since Perl 5.12 and now throws a fatal error. See "Assigning non-zero to $[ is fatal" in perldeprecation. Delimiters must now be graphemes See "Use of unassigned code point or non-standalone grapheme for a delimiter." in perldeprecation Some formerly deprecated uses of an unescaped left brace "{" in regular expression patterns are now illegal But to avoid breaking code unnecessarily, most instances that issued a deprecation warning, remain legal and now have a non-deprecation warning raised. See "Unescaped left braces in regular expressions" in perldeprecation. Previously deprecated sysread()/syswrite() on :utf8 handles is now fatal Calling sysread(), syswrite(), send() or recv() on a ":utf8" handle, whether applied explicitly or implicitly, is now fatal. This was deprecated in perl 5.24. There were two problems with calling these functions on ":utf8" handles: o All four functions only paid attention to the ":utf8" flag. Other layers were completely ignored, so a handle with ":encoding(UTF-16LE)" layer would be treated as UTF-8. Other layers, such as compression are completely ignored with or without the ":utf8" flag. o sysread() and recv() would read from the handle, skipping any validation by the layers, and do no validation of their own. This could lead to invalidly encoded perl scalars. my() in false conditional prohibited Declarations such as "my $x if 0" are no longer permitted. Fatalize $* and $# These special variables, long deprecated, now throw exceptions when used. Fatalize unqualified use of dump() The "dump()" function, long discouraged, may no longer be used unless it is fully qualified, i.e., "CORE::dump()". Remove File::Glob::glob() The "File::Glob::glob()" function, long deprecated, has been removed and now throws an exception which advises use of "File::Glob::bsd_glob()" instead. "pack()" no longer can return malformed UTF-8 It croaks if it would otherwise return a UTF-8 string that contains malformed UTF-8. This protects against potential security threats. This is considered a bug fix as well. Any set of digits in the Common script are legal in a script run of another script There are several sets of digits in the Common script. "[0-9]" is the most familiar. But there are also "[\x{FF10}-\x{FF19}]" (FULLWIDTH DIGIT ZERO - FULLWIDTH DIGIT NINE), and several sets for use in mathematical notation, such as the MATHEMATICAL DOUBLE-STRUCK DIGITs. Any of these sets should be able to appear in script runs of, say, Greek. But the design of 5.30 overlooked all but the ASCII digits "[0-9]", so the design was flawed. This has been fixed, so is both a bug fix and an incompatibility. All digits in a run still have to come from the same set of ten digits. JSON::PP enables allow_nonref by default As JSON::XS 4.0 changed its policy and enabled allow_nonref by default, JSON::PP also enabled allow_nonref by default. Deprecations In XS code, use of various macros dealing with UTF-8. This deprecation was scheduled to become fatal in 5.30, but has been delayed to 5.32 due to problems that showed up with some CPAN modules. For details of what's affected, see perldeprecation. Performance Enhancements o Translating from UTF-8 into the code point it represents now is done via a deterministic finite automaton, speeding it up. As a typical example, "ord("\x7fff")" now requires 12% fewer instructions than before. The performance of checking that a sequence of bytes is valid UTF-8 is similarly improved, again by using a DFA. o Eliminate recursion from finalize_op(). o A handful of small optimizations related to character folding and character classes in regular expressions. o Optimization of "IV" to "UV" conversions. o Speed up of the integer stringification algorithm by processing two digits at a time instead of one. o Improvements based on LGTM analysis and recommendation. o Code optimizations in regcomp.c, regcomp.h, regexec.c. o Regular expression pattern matching of things like "qr/[^a]/" is significantly sped up, where a is any ASCII character. Other classes can get this speed up, but which ones is complicated and depends on the underlying bit patterns of those characters, so differs between ASCII and EBCDIC platforms, but all case pairs, like "qr/[Gg]/" are included, as is "[^01]". module: pkgsrc subject: 'CVS commit: pkgsrc/lang/perl5' unixtime: '1565518458' user: adam