(1) How regex strings are interpolated is a messy business. Usually it DWIM, but you hit a case where it doesn't. See Gory-details-of-parsing-quoted-constructs for more details.

(2), I'd rename one of the x variables or do the interpolation my self: 

my $x = "(quantifier)";
my %x = ( "1" => "(hash_value)" );
my $z = 'quantifier hash_value';

my $ele = $x{1};
print "_$1_\n" if $z =~ /$ele/;

[download]
For the third question, I'd probably play at perturbing perl's probabilistic parser, and not get anywhere :)

-Mark

In reply to Re: Hash Key vs. Quantifier Ambiguity in Regex Context by kvale
in thread Hash Key vs. Quantifier Ambiguity in Regex Context by QM

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.