Your second "anomaly" has to do with foreach loop aliasing. Particularly:


So:
my @a = (1,2,3,4); for my $i (@a) { $i = 5 }; print "@a"; # prints: 5 5 5 5

while:
for my $i (1,2,3,4) { $i = 5 };

errors out with: Modification of a read-only value attempted ...

I think what's happening with your 3 examples of the second anomaly is this:

  1. foreach my $letter ('a' .. 'c', 'd' .. 'f') creates a list of lvalues due to the comma operator in the middle. Perhaps this is done only once at compile time? which explains the persistence.
  2. foreach my $letter ('a' .. 'f') has been optimized as a counting loop, so the range operator does NOT generate a list.
  3. foreach my $letter (@letters) always has @letters redefined right before the loop, so each call to letters() yields consistent results.

In reply to Re: Two Range Operator Anomalies by repellent
in thread Two Range Operator Anomalies by liverpole

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.