Here is how I think about for() assignments:

For a code like,
for ($passed_in) { # inside BLOCK }
Inside the BLOCK, $_ is equal to $$ref where $ref = \$passed_in
Except that if you did change $_, you will also modify $passed_in. They are magically tied together, $_ and the reference, that is.

It is faster this way, since only a REFerence is passed_in. No copy of $passed_in is made. However, for the following code,
for my $scoped_copy ($passed_in) { # inside BLOCK }
A copy of $passed_in is made to $scoped_copy.

The same reasoning above applies to other loop constructs, sub arguments, or CODE BLOCKS of map(), grep(), sort(), etc. for the $_ @_ $a $b variables.

Again, this is just my observation. Would someone with knowledge of Perl guts confirm that I could continue with this train of thought?

In reply to Re: How a for() assignment works by repellent
in thread How a for() assignment works by Herkum

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.