It is not a problem when run as is, because it does not really create a closure when the lexical is declared at the top level outside of any subroutine (I may be wrong, but it's at least a closure that doesn't create any problems...yet). So this works ok:
use strict;
use warnings;
my $foo = 'foo';
bar();
$foo = 'bar';
bar();
sub bar {
print "$foo\n";
}
The problem comes when the script is run under
Apache::Registry, because it turns the script into something like this:
sub foo1234 {
use strict;
use warnings;
my $foo = 'foo';
bar();
$foo = 'bar';
bar();
sub bar {
print "$foo\n";
}
}
# Execute once
foo1234();
# Execute twice
foo1234();
OUTPUT:
foo
bar
bar
bar
This gives you '$foo will not stay shared' warnings, and the result is that '$foo' does not change after the first execution of the subroutine that
Apache::Registry wraps your script in. And mod_perl executes this subroutine over and over again (that's how Apache::Registry keeps your script persistent within mod_perl).
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.