Subs only capture the vars they think they need. They get it wrong in the case sub { eval '$x' }.

In older versions of Perl, the error was silent.

$ perl -wle' sub make { my ($x) = @_; return sub { eval q{$x}; }; } print make(123)->() ' Use of uninitialized value in print at -e line 9.

In newer versions of Perl, the error still exists, but a warning issued.

$ perl -wle' sub make { my ($x) = @_; return sub { eval q{$x}; }; } print make(123)->() ' Variable "$x" is not available at (eval 1) line 2. Use of uninitialized value in print at -e line 9.

The solution is to add a reference to the variable that needs to be captured inside of the anon sub.

$ perl -wle' sub make { my ($x) = @_; return sub { $x if 0; # <--- added eval q{$x}; }; } print make(123)->() ' 123

In reply to Re: Tracking down the source of a new 5.10 warning by ikegami
in thread Tracking down the source of a new 5.10 warning by mpeters

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.