See also The-'lexical_subs'-feature and try

Which is part of the standard language now. :)

> because the inner sub would get bound to one my variable

Basically, it's a 1-to-n problem, because closures are supposed to be created many times.

But named subs are only once assigned globally and bound to a type-glob in the current package (think our ) at compile time (think BEGIN {...} )

Nowthe compiler sees the use of lexical variables from the outer scope, which potentially change with every invocation. (The former are not destroyed) and emits the "won't stay shared" warning.

An anonymous closure sub OTOH would be assigned each time and have a deep-binding to the current outer scope.

Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery


In reply to Re^2: Anonymous subroutines (lexical subs & "will not stay shared") by LanX
in thread Anonymous subroutines by Bod

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.