As dave_the_m mentions, you seem to be a bit confused with your sigils. You know, those funny little characters that go in front of variables in Perl. Your use is consistent with the designs for Perl6, but back here in Perl5 land (i.e. now, not in the future) we still have to use $ when we're accessing a single value and @ when we're accessing a list of values. In both your examples of hash access -- %hash(@array) and %hash{/^foo/} -- you picked the wrong one. Those should be @hash{@array} and $hash{/^foo/}. In the first you have another syntax error, too: those parentheses should be curly brackets. Perhaps it's time to refresh yourself on Perl's syntax. You might find perlcheat to be a handy chart.

HTH

In reply to Re: Assigning regex from arrays to hash keys by revdiablo
in thread Assigning regex from arrays to hash keys by wilbur

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.