Path to this page:
Subject: CVS commit: pkgsrc
From: Adam Ciarcinski
Date: 2013-08-31 17:28:33
Message id: 20130831152833.3500696@cvs.netbsd.org
Log Message:
Changes 5.18.1:
* B has been upgraded from 1.42 to 1.42_01, fixing bugs related to lexical \
subroutines.
* Digest::SHA has been upgraded from 5.84 to 5.84_01, fixing a crashing bug.
* Module::CoreList has been upgraded from 2.89 to 2.96.
* Starting in v5.18.0, a construct like /[#](?{})/x would have its # incorrectly \
interpreted as a comment. The code block would be skipped, unparsed. This has \
been corrected.
* A number of memory leaks related to the new, experimental regexp bracketed \
character class feature have been plugged.
* The OP allocation code now returns correctly aligned memory in all cases for \
struct pmop. Previously it could return memory only aligned to a 4-byte \
boundary, which is not correct for an ithreads build with 64 bit IVs on some 32 \
bit platforms. Notably, this caused the build to fail completely on sparc \
GNU/Linux.
* The debugger's man command been fixed. It was broken in the v5.18.0 release. \
The man command is aliased to the names doc and perldoc - all now work again.
* @_ is now correctly visible in the debugger, fixing a regression introduced in \
v5.18.0's debugger.
* Fixed a small number of regexp constructions that could either fail to match \
or crash perl when the string being matched against was allocated above the 2GB \
line on 32-bit systems.
* Perl v5.16 inadvertently introduced a bug whereby calls to XSUBs that were not \
visible at compile time were treated as lvalues and could be assigned to, even \
when the subroutine was not an lvalue sub. This has been fixed.
* Perl v5.18 inadvertently introduced a bug whereby dual-vars (i.e. variables \
with both string and numeric values, such as $! ) where the truthness of the \
variable was determined by the numeric value rather than the string value.
* Perl v5.18 inadvertently introduced a bug whereby interpolating mixed up- and \
down-graded UTF-8 strings in a regex could result in malformed UTF-8 in the \
pattern: specifically if a downgraded character in the range \x80..\xff followed \
a UTF-8 string
* Lexical constants (my sub a() { 42 }) no longer crash when inlined.
* Parameter prototypes attached to lexical subroutines are now respected when \
compiling sub calls without parentheses. Previously, the prototypes were \
honoured only for calls with parentheses.
* Syntax errors in lexical subroutines in combination with calls to the same \
subroutines no longer cause crashes at compile time.
* The dtrace sub-entry probe now works with lexical subs, instead of crashing
* Undefining an inlinable lexical subroutine (my sub foo() { 42 } undef \
&foo) would result in a crash if warnings were turned on.
* Deep recursion warnings no longer crash lexical subroutines.
Files: