"be consistent" | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
From my understanding of closures, yes, the above sample is
a closure. I reread the Camel (2nd ed. pg. 253) and the example given there is similar, but the one above has added an additional sub (doit) to the mix. It also states that "By and large, closures are not something you need to trouble yourself about." The purpose however is to allow for something to run in the in the context it was initially called outside of that context. Which means you are creating an anonymous sub that will retain its initial values and when you access it at a later point it will "remember" it had a value. In the above example $dave is equal to a sub, it appears that Data::Dumper doesn't handle closures since I ran $dave through the Dumper and it gave me a value of sub { "DUMMY" } hmmmm Any way interesting chunck of code. In reply to Re: Why are closures cool, continued?
by trs80
|
|