While it is true that they are not the same, it does have the benefit of not creating a hash to muck with, as hashes (as nice as they are), do not interpolate. Plus, it does not require a non-standard module to be installed :) Actually this is a really cool trick and will replace my dealings with $1 and $2 in future code, thanks hardburn.

OT, in regard to hashes and why I don't like to use them in some places, does anybody know if Perl6 can/will do the Ruby-esque  print "hash value for key #[$key] is #[$hash{$key}]" ... basically interpolating arbitrary code (even functions) into strings. Would be cool and it definitely cuts down on verbosity of string concatenation.

In reply to Re^3: RFC: named pattern match tokens by SpanishInquisition
in thread RFC: named pattern match tokens by revdiablo

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.