There is no difference in the sequence of when the objects are destroyed, so that doesn't yield much enlightenment.

It looks pretty quirky for the given example, regardless of it possibly being valid if FUNC was called within the the defining local statement.

I don't see the warning is necessary for *this* example.

However, if, in a NESTED call, a "previous definition" of FUNC exists and theoretically could be called to do some function or return a value, from the "outer, non-nested iteration". In that case, the old FUNC is still around and should be usable in the assignment -- the old value of FUNC would be overwritten/redefined BEFORE the old/outer level FUNC had been completely saved off (which, I'm guessing, can't happen until the end of the 'local' statement.

Given that the call to FUNC might not be easily determined while that statement is executing, (multiple local functions could be called, with their existence dependent on external state variables), I'd say the warning is probably necessary, as proving such would seem to be NP-hard.

In reply to Re^11: UPDATED, mostly solved: separation of define + assignment different from combination? by perl-diddler
in thread UPDATED, mostly solved: separation of define + assignment different from combination? by perl-diddler

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.