In perl.git, the branch smoke-me/padthy has been created
<http://perl5.git.perl.org/perl.git/commitdiff/9e5b42b130706dbe567eed3573cb0886c9ea04bd?hp=0000000000000000000000000000000000000000>
at 9e5b42b130706dbe567eed3573cb0886c9ea04bd (commit)
- Log -----------------------------------------------------------------
commit 9e5b42b130706dbe567eed3573cb0886c9ea04bd
Author: Father Chrysostomos <[email protected]>
Date: Tue Sep 23 06:24:50 2014 -0700
Remove most uses of PADMY
SVs_PADMY is now 0, and SvPADMY means !SvPADTMP.
M dump.c
M inline.h
M op.c
M pad.c
M scope.c
M sv.h
commit 7aa096c404cf038ef12bcda0a65852da4ea37e77
Author: Father Chrysostomos <[email protected]>
Date: Tue Sep 23 06:12:05 2014 -0700
Peek.t should not expect PADMY under 5.21.5
M ext/Devel-Peek/t/Peek.t
commit b10f04dd67b8838e457591c3ae45e2666d8bbadb
Author: Father Chrysostomos <[email protected]>
Date: Mon Sep 22 20:25:29 2014 -0700
Stop setting PADMY; renumber PADSTALE
The PADMY flag was originally used on values stored in pads as a way
to mark those slots ase being in use already during pad allocation.
That changed for the most part all the way back in bbce6d6978
(perl5.003_09), but vestiges still remained, because some ops used
PADMY for their targets. I removed the last one yesterday in
14d91147. So the PADMY flag now serves no purpose.
At run time, the sole purpose of PADMY is to determine the meaning of
the flag bit shared by PADTMP and PADSTALE. If PADMY is set, the flag
means the latter. Instead of that more complicated check, we can just
renumber PADSTALE to use the PADMY bit and assume that anything not
PADTMP is PADMY.
This commit changes the flags and does just enough to get
tests passing (except Peek.t).
fixup for padmy flag renumbering
M inline.h
M pad.c
M scope.c
M sv.h
-----------------------------------------------------------------------
--
Perl5 Master Repository
