Hello monks! I come seeking wisdom... or at least proper syntax. I have a hash of arrays like so:
my %whatever = ( 'a' => [1,2,3,4], 'b' => [5,6,7,8], );
normally, I would extract the values in classic camel fashion:
my $extract = $whatever{'a'}[0]; #should = 1
but in this case I'm writing a rule action for the excellent module Parse::RecDescent, so its in another namespace, and must be fully qualified. I tried doing
my $extract = $::whatever{'a'}[0]; #should = 1
and
my $extract = $main::whatever{'a'}[0]; #should = 1
as well as various attempts to play with references, but all to no avail. RecDescent always complains that it must be fully qualified, or I get an undef returned. Anybody experienced this ? Or better yet, know the answer?
Thanks for listening...
Jim

In reply to hashes of arrays in another name space by Anonymous Monk

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.