However AM said that they had a hash of sub names, possibly from a external library.
If you cannot convert the hash of subroutine names to a hash of code references
$s{key}=\&valsub; then use a bare
BLOCK to turn strict off only when calling subs from that hash:
{ # Get an enclosing lexical scope
no strict 'refs'; # allow symbolic refrence shenanigains
&$SubHash{key}(); # Call sub
} # Back to strict 'refs'
or write a sub for this purpose (This assumes $SubHash is a global)
CallFromHash {
no strict 'refs'; # allow symbolic refrence shenanigains
return &$SubHash{shift(@_)}(@_); #Call the sub in the first arg with
+ the rest of @_ as args and return
}
However a hash of sub names is probably a bad idea to start with, and you should reconsider your design to use hard refs (mentioned by
Joost) or remove the hash all together if possible.
Update: Forgot Amperstands
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.