I'm not sure I understand the question. It *sounds* like a question about how to use your editor. Read the manuals for the editor you're using to program. any editor worth using has a "find" and a "repeat last find" facilities.

Or have I misunderstood your question?

perl -e 'print "How sweet does a rose smell? "; chomp ($n = <STDIN>); 
+$rose = "smells sweet to degree $n"; *other_name = *rose; print "$oth
+er_name\n"'
[download]

package foo;
sub one { return 1 };
sub two { return 2 };
sub subs {
    no strict;
    return keys %foo::;
}
[download]

There's no guarantee that methods for that package have been defined outside the .pm file. There's also no guarantee that the .pm file doesn't contain more than one package. Granted both are less than elegant, but still possible.

It expects the name of the file to be searched as the only command line parameter. It will also skip any subroutine whose name begins with an underscore - as I said, this is ripped from a larger program ( the second toy ) doing something similar.

I also cause it to print the line number where the sub definition begins.

#!/usr/bin/perl -w

use strict;
my $source = shift @ARGV || '';
my %keyword = ();

unless ( $source ) {
    print "Usage: $0 <file>\n";
    exit;
}

open SRC, $source or die "Couldn't open $source : $!";
while( <SRC> ) {
    my ( $package, $name );
    $package = $1 if ( ! $package && /^package\s+(.+);/ );

    next unless ( /^sub\s+(.+){\s*$/ );
    $name = $1;

    next if ( substr($name,0,1) eq "_" );

    $name =~ s/\s+$//;
    $keyword{$name} = $.;
}

close SRC;

for ( keys %keyword ) {
    print "$keyword{$_}:$_\n";
}
[download]

Update: Do NOT use Opera for Solaris when submitting - it seems to add a whole lot of newlines. Sorry for the mess.

HTH,
mikfire

-- Randal L. Schwartz, Perl hacker

All of the suggestions you've been given so far are necessarily incomplete. The best you can do is to get a snapshot of the subroutines that are defined in a module's synbol table at a given time. That's not necessarily the complete list of subroutine calls that the module will react to.

In Re: Parse/Validate Code I listed some of the most obvious exceptions that will cause you problems.

Perl Training in the UK <http://www.iterative-software.com>

#!/usr/bin/perl

use strict;

sub sub1 {
    print "In sub1\n";
}

sub sub2 {
    print "In sub2\n";
}

sub sub3 {
    print "In sub3\n";
}

sub MergeHashes {
    my ($hr1, $hr2) = @_;
    my (%retval, $nkey, $key);

    print "hr1 = $hr1, hr2 = $hr2\n";
    foreach $key (keys %{$hr2}){
    $retval{$key} = $$hr2{$key};
    }

    foreach $key (keys %$hr1){
    if (!defined($retval{$key})){
        $retval{$key} = $$hr1{$key};
    }
    }
    
    \%retval;
}

sub showhash {
    my ($hr, $hn) = @_;
    my %hash = %$hr;
    my @subs;

    no strict;

    return if ($checked{$hr});
    $checked{$hr} = 1;
    my $symname;
    foreach $symname (sort keys %hash){
    local *sym = $hash{$symname};


    if (@sym){
        push(@subs, "array $symname");
    } elsif (%sym){
        push(@subs, "hash $symname");
        showhash(\%sym, $symname);
    } elsif (defined(&sym)){
        push(@subs, "sub $symname");
    } else {
        push(@subs, "var $symname");
    }

    }
    if (scalar @subs){
    print "Package $hn => ";
    foreach $symname (sort @subs){
        print "\t", $symname, "\n";
    }
    }
}

my %hash = (
        h1 => {
        a => "A",
        c => "C",
        e => "E",
        g => undef,
        i => undef,
        },

        h2 => {
        a => "A2",
        b => "B",
        d => "D",
        g => "G2",
        h => undef,
        }
        );

showhash(\%main::, "%main::");
[download]

Fooling aside, there is some cool advice here,so I'll add this (possibly redundant) stoopid suggestion:

• If someone else wrote it, you only want to use the subs they mention in the pod. Tinkering with other stuff is not recommended.
• If you wrote it; I advocate using dispatch tables ( a hash of function references ), that way the most you ever have to do is list the keys to the hash containing the functions for that module. There are lotsa reasons for using em.

--

Brother Frankus.

¤