importing 5.12 REGEXP into a old 5.10 perl not yet implemented and tested (REGEXP => PV + Magic) bumped Storable format bin_minor to 8. swapped SX_ERROR and SX_REGEXP because of baked SX_ERROR logic. Still has to think about the necessary support matrix 2.22 | 2.23 ERR | REG REG | -----+------ 5.10 | 5.12 PV+MG| REGEXP in almost all directions, 4*2 = 8 possibilities. Maybe it's just better to freeze a REGEXP in the old PV+Magic format, so that older perls with newer storable files just work. There are apperently two different kinds of REGEXP/pv's. 1. Standalone without a REGCOMP op pointing to the SV (without the PMf_COMPILETIME flag), so we have no op_pmflags to pass to CALLREGCOMP, and 2. the normal with OP, but we cannot support this. We have no association of the SV to the upper OP, only the other way round. Creating a standalone REGEXP does not create the necessary magic chain correctly yet, contrary to a REGCOMP op with REGEXP SV, as done in the B::C or Bytecode compiler. STATUS: make && ../../perl -I../../lib -I../../lib/auto -I. -MStorable \ -e'$a=qr/1/;$Storable::DEBUGME=1;my $b=Storable::dclone($a);"212"=~$b; retrieve got REGEXP(0x159a720) Segmentation fault (core dumped)
CPANPLUS::Config checks 3 specific scenarios first when looking for cpanp-run-perl: parallel to cpanp, parallel to CPANPLUS.pm, or installed into a custom prefix like /tmp/foo. Only *THEN* does it check the the path. If the perl core is extracted to a directory that has cpanp-run-perl installed the same amount of 'uplevels' as the /tmp/foo prefix, we'll pull in the wrong script by accident. Since we set the path to cpanp-run-perl explicitily at the top of this script, it's best to update the config ourselves with a path lookup, rather than rely on its heuristics. Thanks to David Wheeler, Josh Jore and Vincent Pit for helping to track this down. Effects both CPANPLUS and CPANPLUS-Dist-Build
…ids are -1
After the recent, long discussion about this topic and demonstrated cases where the deprecation warnings may actually *break* things, we agreed on IRC to push the "active" deprecation warnings to after 5.12. --Steffen From f1b2d65 Mon Sep 17 00:00:00 2001 From: Steffen Mueller <firstname.lastname@example.org> Date: Mon, 5 Apr 2010 15:12:41 +0200 Subject: [PATCH] Remove deprecation warnings from perl4-era tools The libraries still have deprecation warnings in their comments but the mandatory run-time warnings are disabled until after 5.12.
Moved the single known-failing example to the errata page.
using feature or another (recent) pragma. And previously we had to care only about entereval, but now we can compile to entertry too.
* 'blead' of ssh://perl5.git.perl.org/gitroot/perl: Don't initialize end in pp_reverse when begin is NULL More tests for in-place reverse (empty tied array) Add a test for reversing in-place an empty array Avoid a segfault when reversing an empty array in-place.
This change is a complement to 572558b. Arithmetic on null pointers isn't defined by the C standard, so it may crash even before entering the loop.
Spotted by Tim Jenness
Also trim some trailing whitespace.