This week, a small summary is better than no summary at all.
Rafael Garcia-Suarez finds that h2ph can't process the newest C headers from the glibc, because they include inline functions (instead of good old macros). He forced a bit of heuristics in it to decode the less convoluted C inline functions that might be there. Your mileage may vary.
Roderich Schupp finds that IO::File fails on open a file that is found on another volume on Windows (bug #30132). The problem comes from the Cwd and File::Spec modules (and their handling of volumes in pathnames), on which Ken Williams is working. He released thereafter a new beta of Cwd.pm, on which Mark Mielke provided some performance considerations.
Ton Hospel finds (bug #30237) that the DB_File methods don't behave correctly when they're passed results of substr() in argument. Paul Marquess investigates.
Ton Hospel (again) finds that a small snippet of code involving the
locale pragma, regexp manipulation and loading the
POSIX module at run-time dies with an insecure dependency error when run under -T. (bug #30068). Nobody commented on the possible causes of this regression.
Mathieu Arnold proposed a patch to improve the indentation of the output of Data::Dumper when it is configured to deparse code references (bug #30197).
Perl panics when one tries to use split() on an utf8-string from your average Safe compartment, as Rusty Conover reported (bug #30258). This is probably due to perl trying to load some data behind the scenes, which is forbidden by Safe, so the operation is aborted, and this abortion doesn't end well for some unclear reason.
.. operator is usually optimized in a foreach loop, so that the list is not constructed in place. However, for alphabetic ranges, and when the range is not the only thing in the foreach() argument, this optimization does not occur (bug #30123, reported by Michael G Schwern).
This summary was written by Rafael Garcia-Suarez. Weekly summaries are published on http://use.perl.org/ and posted on a mailing list, which subscription address is email@example.com. Comments and corrections welcome.