Thanks, I forgot about scope-exit behavior...

Anyway I'm wondering why a post-fix if doesn't force a new scope, IMHO that would solve the problem in a consistent way:

use strict;
use warnings;
 
$a=0;
 
if ($a) {
  my $z=666;
}
 
my $y=666 if $a;
 
print $y;         # -> nothing
print $z;         # -> Global symbol "$z" requires explicit package na
+me

[download]

of course treating short circuit and in the same way could cause more complications.

$a and my $x =666;
print $x;        # -> nothing

[download]

At least this "it's a new scope" logic could be used to detect "my"-problems at compile-time and throw warnings.

Cheers Rolf

UPDATE: short-circuit and

In reply to Re^2: A curious case of of my() by LanX
in thread A curious case of of my() by fleetingflicker

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.