Here's the start of one way to roll up your own plugin manager:

use strict;
use warnings;

my %plugins;

opendir DIR, ".";

# Search for plugins
while ($_ = readdir DIR) {
    next unless m|(plugin_[^\\/]+)\.pm$|;
    next unless -f $_;
    
    my $plugin = $1;
    next unless require "$plugin.pm";
    $plugins{$plugin} = "${plugin}::";
}

closedir DIR;

# Run the 'run' sub from each plugin found
for (keys %plugins) {
    no strict "refs";
    "$plugins{$_}run"->();
}

-------- 8< -----------
# plugin_hi.pm

use strict;
use warnings;

package plugin_hi;

sub run {
    print "Hi\n";
}

1;

-------- 8< -----------
# plugin_hello.pm

use strict;
use warnings;

package plugin_hello;

sub run {
    print "Hello\n";
}

1;
[download]

Prints:

Hello
Hi
[download]

Plenty of scope for improvement here. Having the plugins provide objects would be a big improvement in many ways for example.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.