NAME Sub::Recursive - Anonymous memory leak free recursive subroutines SYNOPSIS use Sub::Recursive; # Fast LEAK FREE recursive closure. my $fac = recursive { my ($n) = @_; return 1 if $n < 1; return $n * $REC->($n - 1); }; # Recursive anonymous definition in one line, plus invocation. print recursive { $_[0] <= 1 ? 1 : $_[0] * $REC->($_[0] - 1) } -> (5); ######################################## use Sub::Recursive '_'; # Slow named recursive function. Uses Perl 6's magical &_ subroutine. sub fac { my ($n) = @_; return 1 if $n < 1; return $n * _($n - 1); } ######################################## use Sub::Recursive 'recursive_'; # Exactly the same code between the braces as for &fac. # Really slow. # Note the trailing underscore on recursive_. my $slow_and_bad = recursive_ { my ($n) = @_; return 1 if $n < 1; return $n * _($n - 1); }; DESCRIPTION Recursive closures suffer from a severe memory leak. "Sub::Recursive" makes the problem go away cleanly and at the same time allows you to write recursive subroutines as expression and can make them truly anonymous. There's no significant speed difference between using &recursive and writing the simpler leaking solution. This module has been extended to also provide the Perl 6 &_ magical subroutine. It is an alias for the current subroutine. I don't recommend anyone to use &_ in Perl 5, but now you at least can taste it. The problem The following won't work: my $fac = sub { my ($n) = @_; return 1 if $n < 1; return $n * $fac->($n - 1); }; because of the recursive use of $fac which isn't available until after the statement. The common fix is to do my $fac; $fac = sub { my ($n) = @_; return 1 if $n < 1; return $n * $fac->($n - 1); }; Unfortunately, you introduce another problem. Because of perl's reference count system, the code above is a memory leak. $fac references the anonymous sub which references $fac, thus creating a circular reference. This module does not suffer from that memory leak. There are two more reasons why I don't like to write recursive closures like that: (a) you have to first declare it, then assign it thus requiring more than a simple expression (b) you have to name it one way or another. The solution This module fixes all those issues. Just change "sub" for "recursive" and use &$REC for the recursive call: use Sub::Recursive; my $fac = recursive { my ($n) = @_; return 1 if $n < 1; return $n * $REC->($n - 1); }; Note that you don't even have to give it a name. You can e.g. pass it directly to a subroutine, foo(recursive { ... }); just as any other anonymous subroutine. EXPORTS If no arguments are given to the "use" statement $REC and &recursive are exported. If any arguments are given only those given are exported. $REC - exported by default $REC holds a reference to the current subroutine for subroutines created with &recursive. "recursive" - exported by default &recursive takes one argument and that's an anonymous sub. It's prototyped with "&" so bare-block calling style is allowed: recursive { ... } The return value is an anonymous closure that has &$REC working in it. "recursive_" &recursive_ is like &recursive except that &_ is used instead of &$REC. It also implies "_" in the import list. Subroutines created with &recursive_ are very slow and the "caller" traceback will contain doubly function calls for every call to the anonymous subroutine. "_" &_ isn't exactly exported, it's just defined. The name "_" is forced into the main namespace so all packages use the same variable. This is why $_ works the way it works. So by introducing &_ in your package you introduce it in every package--not that I think that any other package defines &_... Don't use this is serious code. EXAMPLE Some algorithms are perhaps best written recursively. For simplicity, let's say I have a tree consisting of arrays of array with arbitrary depth. I want to map over this data structure, translating every value to another. For this I use my $translator = recursive { [ map { ref() ? $REC->($_) : do { $translate{$_} } } @{$_[0]} ] }; my $bar = $translator->($foo); Now, a tree mapper isn't perhaps the best example as it's a pretty general problem to solve, and should perhaps be abstracted but it still serves as an example of how this module can be handy. A similar but more specialized task would be to find all men who share their Y chromosome. # A person data structure look like this. my $person = { name => ..., sons => [ ... ], # objects like $person daughters => [ ... ], # objects like $person }; my @names = recursive { my ($person) = @_; $person->{name}, map $REC->($_), @{$person->{sons}} } -> ($forefather); This particular example isn't a closure as it doesn't reference any lexicals outside itself (and thus could've been written as a named subroutine). It's easy enough to think of a case when it would be a closure though. For instance if some branches should be excluded. A simple flag would solve that. my %exclude = ...; my @names = recursive { my ($person) = @_; return if $exclude{$person}; $person->{name}, map $REC->($_), @{$person->{sons}} } -> ($forefather); Hopefully this illustrates how this module allows you to write recursive algorithms inline like any other algorithm. DIAGNOSTICS Can't use &_ on unrecursive anonymous subroutine (F) Change "sub" to "recursive_" in the definition. &_ is already defined by someone else (W|S) You wanted this module to define &_ but it was already defined by someone else. &_ was redefined to be what you asked for. WARNING Using &_ is slow! REALLY REALLY SLOW!!! See misc/bench.pl in this distribution. Using &$REC however is just as fast as not using this module and solving the problem manually. Don't get the habit of using "recursive" instead of "sub" though then "sub" is enough as it imposes an overhead. AUTHOR Johan Lodin COPYRIGHT Copyright 2004 Johan Lodin. All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO perlref