comment on

Since your subs all seem to take a CGI instance as an argument, you could subclass CGI.pm as Site::CGI and use that instead of CGI.pm in the top level scripts. That would help prevent putting functions with dissimilar purposes in your Common.pm.

The subclassing mechanism is not too difficult. The basic steps are:

package Site::CGI;

use CGI;
@ISA = qw/CGI/;

# subroutine definitions, object instance is first arg
# . . .

1;
[download]

Save that file as Site/CGI.pm somewhere in your @INC path.

You would then, in top level scripts, say,

use Site::CGI;  # instead of use CGI;
my $query = Site::CGI->new;

# . . .

print $query->my_sub;

# etc
[download]

After Compline,
Zaxo

In reply to Re: Converting common subroutines as a module by Zaxo
in thread Converting common subroutines as a module by sara2005

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks