Here is one potential solution (just wrap it in a sub and tweak a litle), if you insist on having a single master pod file for all your apps.

use Pod::POM;
use Pod::POM::View::Text;

my $view = Pod::POM::View::Text->new();
my $parser = Pod::POM->new();

# parse from text or file 
my $pom = $parser->parse_file(__FILE__) || die $parser->error();

# examine any warnings raised
for my $warning ($parser->warnings()) {
    warn $warning, "\n";
}


#use Data::Dumper; die Dumper $pom; # in case you wanna know what it l
+ooks like


for my $head1 ($pom->head1()) {
    if( $head1->title() =~ /Popcorn app/i ) {
        print $head1->present($view); # display as text
## same thing
#        print $view->print($head1);
#        print Pod::POM::View::Text->print($head1);
        last;# bust out of the for loop
    }
}



__DATA__

=head1 Butter app

Butter app does this'n'that, and this'n'this

=head2 Options

blah blah

=head1 Popcorn app

Popcorn app does this'n'that, and this'n'this

=head2 Options

blah blah

=head1 Fudge app

Fudge app does this'n'that, and this'n'this

=head2 Options

blah blah

=cut
[download]

It is important to note that Pod::POM has a few minor logic flaws, but for casual pod it doesn't matter. Pod::POM does not handle =begin format/=end format correctly. It insists on searching the stuff in between for Formatting Codes, which it shouldn't do except in special circumstances. I rather like the module, and have contacted the author about this problem.

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! ** The Third rule of perl club is a statement of fact: pod is sexy.