A closure closes over the current lexical environment. That does not mean that the current lexical environment is private, whatever else shares it can change it.

When I said a closure "protect[s] it from the outside," I meant from outside the lexical scope that was closed around. I probably should have spelled this out more explicitly, as you have.

In the case of our, the current lexical environment includes the fact that certain variables are actually the equivalent package variable.

Ah, yes. Thanks for the clarification on this. So the closure does not contain the variable per se, but just the alias to it that our created.

In reply to Re^5: "our" versus "my" for class data by revdiablo
in thread "our" versus "my" for class data by mp

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.