|We don't bite newbies here... much|
Re^3: Reference to guard not releasedby perl-diddler (Hermit)
|on Jul 19, 2012 at 00:23 UTC||Need Help??|
So what is ScopeGuard supposed to be guarding? "$x"?
You declared $x at the global level. Is that what you are protecting? That doesn't get destroyed until the program exits...
You declared an anonymous sub inside scopeguardnew... that's also unlikely to be destroyed until your program exits -- because Scope::Guard is holding a "reference" to the interior sub (likely)... and, AT THE LEAST, the 'my $x' is declared at the global level -- so it won't be destroyed until the prog exits...
But I checked, and putting braces around the dcl of $x, doesn't change the output. So I would bet scopeguard has stored a reference to the interior sub so it can be called when "$x" goes out of scope.
But you referenced "$x" in side the sub that scope guard stored...--- so $x can't go out of scope until the interior sub (that you passed to SG->new) disappears -- and it won't disappear until your prog exits...
All you did by assigning undef to $code is lose the reference to the outside sub.. SGnew still has a reference to the inner sub and $x...
The reference to $x, that is in the anonymous sub, is referred to in jargon, as a "closure".
I'd guess that's because it creates a closed "ecosystem" that holds the anon-sub and the anon-sub's copy of $x -- no one changing '$x', after that sub is defined, will affect the value that is stored (referenced, really), in that inner sub (inside the new)...
Does that make more sense?