Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Re^2: Closure warning with Perl 5.14?

by SimonClinch (Chaplain)
on May 19, 2011 at 11:35 UTC ( #905675=note: print w/ replies, xml ) Need Help??

in reply to Re: Closure warning with Perl 5.14?
in thread Closure warning with Perl 5.14?

By coincidence I have been having a similar problem in 5.8.2. When assigning a variable to a match backreference, at outer scope there was no warning when the match failed. When assigning it to a variable at level 1 loop scope from within a level 2 loop, it gave the warning that something was uninitialised in the match expression (an untrue statement). Furthermore, even using the ternary operator to force the variable to '' on match failure, the match warning was delayed until the variable was subsequently tested with a simple "if ($var)" at which point it made even less sense. I get the impression that Perl can sometimes catch its feet slightly when trying to process potential uninitialisation for variables being updated or initialised in a different lexical and sub-global scope from which they were declared.

One world, one people

Comment on Re^2: Closure warning with Perl 5.14?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://905675]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (4)
As of 2015-10-04 20:45 GMT
Find Nodes?
    Voting Booth?

    Does Humor Belong in Programming?

    Results (104 votes), past polls