many string evals cause eventual scope issues
authorDavid Mitchell <davem@iabyn.com>
Sun, 6 Feb 2011 14:34:49 +0000 (14:34 +0000)
committerDavid Mitchell <davem@iabyn.com>
Sun, 6 Feb 2011 18:57:16 +0000 (18:57 +0000)
commitd1bfb649a8c4cc0b39b0fd6371c009b71c0b497f
treec74e8e6b86235040df01c6223913c1f300dd96ae
parent5bcf08c4547e5c6ec79e3cc699bedecb80c1a756
many string evals cause eventual scope issues

[perl #83364]. PL_cop_seqmax is U32 but PAD_MAX was defined as
I32_MAX. Once PL_cop_seqmax got above 2 billion it would start to appear
spuriosuly as if  PL_cop_seqmax > PAD_MAX, so the scope of lexical vars in
evals etc went awry.

Also replaces a use of ~0 with PAD_MAX, which shouldn't change anything,
but is just tidier.
pad.c