You cannot use local on lexically scoped variables. This is a totally artificial restriction but it means that in those (rare) ocasions when the semantics of local are the tidiest way to implement something you need to use package variables.

Perl does not support nested named subroutines. If you need nested subroutines you can use anonymous subroutines but this makes stackdumps nigh-on unreadable. Using file-scoped lexicals with local() would be a solution but as I said before you can't do that. So the next best thing is our().

I once wrote some twisted recursive code to render tables of tables in HTML. Sometimes it would cluck() and I'd get a backtrace with a dozen levels of anonynous subroutine.

use AtExit;

sub awful {
    my ($various,%shared,@vars);
    my ($recusive1,$recursive2);
    my $cleanup = AtExit->new(sub{
        undef $recursive1;
        undef $recursive2;
    });
    $recursive1 = sub {
        # Do stuff with $various,%shared,@vars and make further calls 
+to
        # $recursive1->() and $recursive2->()
    }
    $recursive2 = sub {
        # Do stuff with $various,%shared,@vars and make further calls 
+to
        # $recursive1->() and &$recursive2->() and call
    frobnicate($recursive1);
    }
    $recursive1->();
}
[download]

I decided it was more maintainable as:

our ($various,%shared,@vars);

sub awful {
    local ($various,%shared,@vars);
    recursive1();
}

sub recursive1 {
    # Do stuff with $various,%shared,@vars and make further calls to
    # recursive1() and recursive2()
}

sub recursive2 {
    # Do stuff with $various,%shared,@vars and make further calls to
    # recursive1() and recursive2()
    frobnicate(\&recursive1);
}
[download]

Note that frobnicate may call awful() but this inner awful() would not want to share the outer awful()'s variables.

Now there is a potential problem here if frobnicate() store its CODE reference argument somewhere and thus manages to call back to recursive1() after awful() completes or for that matter during a reentrant call of awful(). But I happened to know that wasn't going to happen.

---

There's a similar problem to the nested subroutine problem with regex containing (?{}) except you don't get the warning.

use strict;
use warnings;

sub foo {
    my $x = shift;
    print "$x ";
    sub foo1 { 
      print "$x "; # Warning
    } 
    foo1();
    '' =~ /(?{ print "$x\n" })/; # No warning
}
foo('Hello');   # Prints 'Hello Hello Hello'
foo('Goodbye'); # Prints 'Goodbye Hello Hello'

sub bar {
    local our $x = shift;
    print "$x ";
    sub bar1 { 
      print "$x ";
    } 
    bar1();
    '' =~ /(?{ print "$x\n" })/;
}

bar('Hello');   # Prints 'Hello Hello Hello'
bar('Goodbye'); # Prints 'Goodbye Goodbye Goodbye'
__END__
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.