print(my $x = 1234) if COND;
Which is to say, they probably didn't want to step on anything that has remote chance of being legit. | [reply]
[d/l] |
But my $x if COND; doesn't warn either, unless COND is false. Not sure what print(my $x = 1234) if 0; would be good for. Note also that print(my $x = 1234) if COND; does not have a my $x = EXPR if COND subexpression, not even on a textual level.
| [reply]
[d/l]
[select] |
That was a hack for getting state variables. So it might be found in code that should use state instead, and won't work as expected in the new versions. | [reply]
[d/l] |
Yeah, but what is the intention of all other code that uses:
my $var if COND;
? Either the if COND is redundant, because it's always true, or it maybe false and you have the same issue. Also,
my $var = 0 if 0;
creates a "state" variable, yet there's no warning.
Now, I'm usually not a fan of adding a warning for every little thing, but if there's a warning, it shouldn't be inconsistent on when it warns and when it doesn't. | [reply]
[d/l]
[select] |
Oh well.
I agree with your sentiment.
We could speculate about some code path or another that the warning was added to. But in general, if it was added to some specific code path in the perl implementation, it was either (1)he was working in that part of the code and added the warning because he could, (2) that specific path is one that changed its behavior under that circumstance, or (3) adding it there as opposed to systematically was low-hanging fruit.
| [reply] |
