Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

Re: anonymous vs named subroutines as closures

by ikegami (Pope)
on Jun 04, 2013 at 04:16 UTC ( #1036884=note: print w/ replies, xml ) Need Help??


in reply to anonymous vs named subroutines as closures

Demonstration of "will not stay shared":

sub outer { my ($x) = @_; sub inner { say $x; } inner(); } # Warns Variable "$x" will not stay shared outer(4); # Prints 4 outer(6); # Prints 4!!!

Here's what's going on.

sub named { ... }

is more or less the same as

BEGIN { *named = sub { ... }; }

As such, it only captures once, when the sub is compiled.

In the above code, when outer goes out of scope, $x would normally be cleared. But since the closure still references it, a new $x is a created instead. From this point on, the $x in inner is different from the $x is outer; it "didn't stay shared".


Comment on Re: anonymous vs named subroutines as closures
Select or Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1036884]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (7)
As of 2015-07-04 21:52 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (60 votes), past polls