Hi rje!
I have experience with reinventing the wheel on this type of thing ( wrote a Java parallel processing framework from scratch )</brag> and I think that its not going to be a lot of work ( you have a good idea for it ) and that you'll have fun doing it.
You might do something like this:
opendir( DIR, $command-directory ) || die "cant open dir: $!";
@commands = readdir( DIR );
@commands = grep( m!\.pm$!, @commands ); # only .pm files
$torun = "thetime";
$arg1 = '.....';
$arg2 = 'etc.';
foreach ( @commands )
{
if( $_ eq $torun ){ $continue = 'true' }
else{ $continue = undef }
}
if( defined( $continue ) )
{
require ("$torun" . "\.pm");
${$torun}::{$torun}->( $arg1, $arg2 ); # run subroutine $torun i
+n file $torun.pm
}
if( !defined( $continue ) )
{
print "no such method call: $torun\n";
}
You could have the procedure subroutine and file share the same name. * only key parts are tested. Good luck!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|