diff options
author | Father Chrysostomos <sprout@cpan.org> | 2016-07-30 19:37:04 -0700 |
---|---|---|
committer | Father Chrysostomos <sprout@cpan.org> | 2016-07-31 06:35:04 -0700 |
commit | 7bb33634741e6401456a85c49eb51fe0fc1aefc7 (patch) | |
tree | 778f0ff96762e17e730aa67b5941560c6b079709 /gv.c | |
parent | fc273927378ed6a1a60a5758f7e36713630d5e13 (diff) | |
download | perl-7bb33634741e6401456a85c49eb51fe0fc1aefc7.tar.gz |
Exempt @DB::args from ‘used once’ warnings
A perfectly benign use of @DB::args like
sub foo { package DB { () = caller 0 } print "@DB::args\n" }
foo(1..3);
warns under -w, though that is exactly its intended use. That is
is not nice.
warnings.pm itself uses @DB::args, which is why this went unnoticed
for so many years.
This commit eliminates the ‘used once’ warning, but the ‘Possible
unintended interpolation’ message that that code produces will be
handled in another commit.
Diffstat (limited to 'gv.c')
-rw-r--r-- | gv.c | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -1831,6 +1831,10 @@ S_gv_magicalize(pTHX_ GV *gv, HV *stash, const char *name, STRLEN len, GvMULTI_on(gv); break; case 'a': + if (stash == PL_debstash && len==4 && strEQ(name2,"rgs")) { + GvMULTI_on(gv_AVadd(gv)); + break; + } case 'b': if (len == 1 && sv_type == SVt_PV) GvMULTI_on(gv); |