I think you are going in the whole wrong direction. Coordinated arrays is not a good idea for starters. See if you can follow how/why this works and go from there

use strict; use warnings; my @sets; push @sets,{name=>'Country',api=>'get_country()'}; push @sets,{name=>'State' ,api=>'get_state()'}; push @sets,{name=>'fake' ,api=>'get_fake()'}; my %subs; $subs{'get_country()'}=\&get_country; $subs{'get_state()'} =\&get_state; for my $set (@sets) { my $vname=$set->{name}; my $api =$set->{api}; my $call=$subs{$api}; my $res; if (defined $call) {$res=&$call;} $set->{res}=$res; } use Data::Dumper; print Dumper (\@sets); exit; sub get_country{ return 'USA'; } sub get_state{ return 'FL'; }


In reply to Re: Supplementary Google GA question by huck
in thread Supplementary Google GA question by Laurielounge

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.