in reply to Re: A 'print' at one spot changes a value at another
in thread A 'print' at one spot changes a value at another

I can't reproduce the "closure" warning; only the "uninitialized" one. I tried it on 5.8.3 and 5.8.6. Can you give more details (e.g. perl version, any changes to the code, etc.)? Thanks!

the lowliest monk

  • Comment on Re^2: A 'print' at one spot changes a value at another

Replies are listed 'Best First'.
Re^3: A 'print' at one spot changes a value at another
by dave_the_m (Monsignor) on Aug 15, 2005 at 09:36 UTC
    That warning only appears in bleedperl, ie 5.9.x

    update: To be precise, as of change #19637, "jumbo closure fix"

    Dave.

      Is this not a third reason? If so, perldiag should be fixed.
        Is this not a third reason? If so, perldiag should be fixed
        I don't think so. The two fundamantal causes of the warning are that the variable doesn't yet exist, or that it exists but has gone out of scope. The OP's code is trying to access a variable that has gone out of scope - ie a file-scoped lexical that goes out of scope at the end of executing the require'd file

        Dave.