Sure, you can store perl code as a string in a file or a database. Here is an example of how to turn it into a sub.

$code = "print 'Hello World.'";  # This may have come for your DB
$sub = eval "sub { $code }"; # use eval and string interpolation to co
+nvert it into an anon. sub
$sub->(); # Execute the sub;

# To pass arguments to the sub, do this:
$sub->($a1, $a2); #etc

# You can capture the return value too
$ret = $sub->();

[download]

Update: I almost forgot to warn you: be very careful with who has access to the string version of the perl code. Obviously, if that data came from an untrusted source, they could destroy your system!

Ted Young

($$<<$$=>$$<=>$$<=$$>>$$) always returns 1. :-)

In reply to Re: Creating subroutines on the fly by TedYoung
in thread Creating subroutines on the fly by pander

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.