RE: Should MY:: be a real symbol table?

[Dave Mitchell]

Dan Sugalski <[EMAIL PROTECTED]> wrote:
> This also makes scope entry and exit costlier, since you need to make a 
> savestack entry and restore, respectively, for each lexical. I don't think 
> it'd be a win, even if closures weren't getting in your way.

although to be fair, the current run-time action of my() is to push a
"remember to clear me at the the end" note onto the savestack - not
quite as much work as pushing the old SV onto the savestack and
allocating a new SV, but work nevertheless.