I've become persuaded that the current behavior should be kept. It is deducible from operator precedence and, once known, is not the cause of any great confusion.
Somewhat agree. The existing behaviour is also IMO easier to document clearly than with the proposed change.

But to throw fuel on the fire: 

$ perl -wl
$x = "abc";
for $z (substr($x,1,1)) { print ":$z:"; $z = "zz"; print ":$z:" }
__END__
:b:
:z:

[download]
If you alias something to the substr or pass it as a parameter, you can get some pretty odd results currently. OTOH, this is not a lot different from this case: 
"abc"=~/.(.)/;
for $z ($1) { print ":$z:"; "zz" =~ /.(.)/; print ":$z:" }

[download]

In reply to Re: Re: lvalue substring oddities by ysth
in thread lvalue substring oddities by ysth

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.