The lexical variable in your example is in the package scope.

Compare this:

package foo; our $n = 1; package main; print "n = ", $foo::n , $/; # n = 1
With this:
package foo; my $n = 1; package main; print "n = ", $foo::n , $/; # nothing

A related topic is the behaviour of closures, which was mentioned by several other monks above. One of the less obvious behaviours of closures can be seen in the following example:

sub foo { my $n = 1; print $n; bar(); print $n; bar(); sub bar { $n++; } } foo(); foo(); #output 1211
The inner sub 'bar' keeps a reference to the instance of '$n' that existed during the first call to 'foo'. People frequently run into this problem when they first start using mod_perl with Apache::Registry, as documented here:
mod_perl / Apache::Registry accidental closures

In reply to Re: Using an "outer" lexical in a sub? by imp
in thread Using an "outer" lexical in a sub? by cornballer

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



  • 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:
    & &amp;
    < &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.