I have used no strict "refs" here, the code works fine that way, and that is wrong. The code works great though, i just want the correct syntax.
You seem to have the impression use strict forbids incorrect syntax. It doesn't. If the syntax isn't correct, the compiler will barf. strict will prevent you from using certain syntactically correct constructs.

Your snippit doesn't give me enough context to determine whether there's a good solution that avoids using strings as function names. (You could use the PACKAGE->$function_name syntax, and shift off the first argument in the function, but that doesn't buy you anything - it will still come with all the drawbacks of &$function_name).

In reply to Re: use strict refs unless you can't figure out the syntax by JavaFan
in thread use strict refs unless you can't figure out the syntax by theleftsock

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.