++ Nice summary.
Minor niggle. If it were me I would put a little bit more emphasis on lexical scoping and a little less emphasis on reference counting. When the value of a lexical variable is garbage collected is independent of whether a Perl closure is created. It's about scope - not memory usage. For example:
our $Global;
sub make_closure {
my %lexical;
$Global = \%lexical;
return sub {
my $key = shift;
@_ ? $lexical{$key} = shift : $lexical{$key};
};
};
{
# here we make a closure
my $c = make_closure();
# which we can use to set and get keys
$c->(foo => 42);
print "foo is ", $c->('foo'), "\n";
# at the end of the scope the closure goes away
};
# but the referant is still around
print "Global foo is ", $Global->{foo}, "\n";
Update: It might also be worth comparing what Perl does to languages without lexical capture like C.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|