I suppose I could have written that without looping twice over grep. I had this thought of verifying that all the rules matched something since it might be considered an error condition to attempt to replace lexicals that don't exist. Then again, in a forest of indexed lists (PADLIST zero is the names, >=one is the pads, on each component of PADLIST only the index 1+ is interesting, etc) the whole thought is on doing everything indexed. The only remaining problem is that there is no guarantee that your two shifts execute in any particular order since you didn't separate the two modifications to @_ into two statements. You might get the replacement first and then the rule.

my @replacements; my @rules; for ( 0 .. $#replacement_pairs ) { push @{ $_ & 1 ? \@replacements : \@rules }, $replacement_pairs[$_]; }

In reply to Re: Re: Re: Re: Rebinding closures by diotalevi
in thread Rebinding closures by diotalevi

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.