asked on

Perl Module .pm changes

I would like to update my Perl Module (.pm) file. I made the changes using vi. My OS is Red Hat 5.3, but when I run through the functionality of the script, it appears that it is not working or taking affect.

I am guessing I need to do something more than just edit the .pm file, but I am really at a loss here. Any help would be appreciated.

The script does not reside in the default Perl directory. I am also using Perl v5.8.8

wilcoxon

It sounds like you have another copy of the module somewhere. You need to determine where that is and copy your updated module there. You should be able to add something like this at the top of your script...

use My::Module;
foreach my $dir (@INC) {
    print "found in $dir\n" if (-f "$dir/My/Module.pm");
}

Open in new window

Randy Peterson

ASKER

Here is my file header: I am absolutely new to this, so I am trying to figure this all out. I have searched for the modules, but never found it. I just do not ever see any changes take affect.

#file:Apache2/WapGateway.pm
#-----------------------

package Apache2::WapGateway;

use strict;
use warnings;
use DBI;
use Socket;

use Apache2::RequestRec ();
use Apache2::Connection ();
use Apache2::RequestIO ();
use Apache2::RequestUtil ();
use Apache2::ServerUtil ();
use Apache2::ServerRec ();
use Apache2::Process ();
use APR::Table ();

use Apache2::Const -compile => qw(FORBIDDEN DECLINED PROXYREQ_PROXY REDIRECT OK);

ASKER CERTIFIED SOLUTION

FishMonger

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

wilcoxon

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Randy Peterson

ASKER

I am agreeing with what you both are saying. I unfortunately cannot restart Apache until a maintenance window tonight, so I will try to do so then and hopefully credit you for the answer. Thanks.

Randy Peterson

ASKER

You were right. A restart of the Apache server caused the script to be re-read in. Thanks.