Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

A closure is a subroutine that makes use of a lexical variable defined outside the subroutine. For example:

use v5.14; my $foo = 40; sub foo { return(2 + $foo); }

The foo() sub is said to be a "closure", and the $foo variable has be "closed over".

When most people talk about closures though, they are usually referring to anonymous functions rather than named ones like above. Something like:

use v5.14; sub get_counter { my ($count) = @_; my $closure = sub { $count++ }; return $closure; } my $counter = get_counter(40); my $other = get_counter(99); say $counter->(); say $other->(); say $counter->(); say $other->(); say $counter->();

In fact, people often use the word "closures" to refer to anonymous functions even if the function doesn't close over any variables!

This is probably due to the fact that in most programming languages (including Perl) there's no syntactic difference between defining an anonymous sub that closes over a variable verses one that does not. They are implemented subtly differently internally though as can be seen by this example:

use v5.14; use Scalar::Util qw/refaddr/; my @closures; my @nonclosures; for my $i (qw/ a b c /) { push @closures, sub { $i }; push @nonclosures, sub { 42 }; } say join "|" => map refaddr($_), @closures; say join "|" => map refaddr($_), @nonclosures;

You'll notice that the three non-closure coderefs share a reference address. This is an optimization that Perl does. (I have at least twice had to work around this optimization by defining a dummy variable and closing over it. But then again, I do a lot of weird stuff in Perl. Most people probably never need to care about this difference.)

Anyway, coming back to Data::Form::Validator - it does accept coderefs as arguments in some places. Whether those coderefs are technically closures (i.e. they close over external variables), it probably doesn't care.

In reply to Re: Closure - Perl Perspective by tobyink
in thread Closure - Perl Perspective by perlron

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others rifling through the Monastery: (3)
As of 2022-05-18 17:18 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (71 votes). Check out past polls.