OK, the penny is dropping...

So the @_ is an array of SV*. To distinguish aliases as arguments requires the pointer, not the target, to be marked -- it's only assignments via the alias that should be trapped. That would add overhead.

Mind you, the compiler knows when it's assigning to $_[x], and only then does it need to worry about copies of aliases -- I think the propagation of aliases is limited -- so I guess the overhead could be contained... assuming one could figure out a way of passing the information with the pointer. Hmmm. I'm starting to feel queasy.

Well, nothing's perfect... if the 99% cases (lexically inside the foreach/map/etc) were trapped at compile-time it would be a step in the right direction.


In reply to Re^9: Changing array by changing $_? by gone2015
in thread Changing array by changing $_? by johnvandam

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.