Re^5: PadWalker's closed_over - but for our variables?

You know I'm picky about terminology, calling my "private" and package vars "public" would have been better.

I'm not an expert on the theory and terminology, I'm an engineer and I care more about how things work ;-)

Solutions are available by parsing the optree like demonstrated in B::Xref B::Concise and B::Deparse

Yes, I was thinking about these too, it's too bad none of them provide exactly what you want already. B::Xref seems like a decent starting point, unless of course someone has done this already (I don't know yet).

Comment on Re^5: PadWalker's closed_over - but for our variables? Download Code

Replies are listed 'Best First'.
Re^6: PadWalker's closed_over - but for our variables? by LanX (Saint) on Apr 03, 2021 at 18:19 UTC
> I'm not an expert on the theory and terminology, I'm an engineer and I care more about how things work ;-) OK Wolowitz, but we can agree that wording matters in communication? ;-) > B::Xref seems like a decent starting point unfortunately it's buggy, I'd rather try to reverse "engineer" B::Deparse. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]