You can do that in a very light weight way by creating a package for each feed type. They can be in a single file or multiple files or even the main file. If not in the main file you can use or require as suits your purpose then create an instance of the appropriate type. Consider:

use strict;
use warnings;

package FetchOne;

sub new {
    my ($class, %params) = @_;

    return bless\%params, $class;
}

sub type {
    return 'Fetch type One';
}

package FetchTwo;

sub new {
    my ($class, %params) = @_;

    return bless\%params, $class;
}

sub type {
    return 'Fetch type Two';
}

package main;

my $type = 'Two';
my $obj = "Fetch$type"->new();

print $obj->type();
[download]

Prints:

Fetch type Two
[download]

use Module::Load;

...

   load $package;
   my $obj= $package->new( %options );
   $obj->do_something;
[download]

No need for awkward cross-package function-calls.

Maybe GrandFather wanted to recommend a plugin-supporting module (e.g. Module::Pluggable)?

geoffleach:

Your question already seems to be solved, but I thought I'd post a note with respect to your original problem and the use case you're describing here. The name of the file and the name of the package inside it isn't necessarily related. That's one of the difficulties that I expect Grandfather and others were thinking about.

So one thing you can do is use the same package name for all of your podcast processors. Then you can do something like:

$podcast_name = 'comedy_with_joe';
require "podcast_processors/${podcast_name}.pm";
PodcastProcessor::somesub();
[download]

where each of your podcast processor modules would look like:

# process podcasts for XYZ
package PodcastProcessor;

... yadda ...

sub somesub { ... }
[download]

...roboticus

When your only tool is a hammer, all problems look like your thumb.