That design will give you trouble. It will be confusing to understand and maintain.

I recommend passing the frame data as arguments to the functions:

my (%frame_lookup_by) = ( 21 => { desc => "S/W Status", value => sub { $_[0]*256 + $_[1]} , }, 33 => { desc => "HK Subcom", value => sub { $_[1] % 16 }, #modulo 16 of w12 }, 117 => { desc => "General Status", value => sub {$_[0]*256 + $_[1] }, }, 129 => { desc => "Sensor Status", value => sub { $_[0]*256 + $_[1] }, }, );
With that you can supply the argument that's in the current scope like so:
my $result = $ref_frame_lookup_by{33}->{value}->(@minor_frame_data);

After Compline,
Zaxo


In reply to Re: Updating hash of subroutines by Zaxo
in thread Updating hash of subroutines 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.