Move the methods into a base class and keep the functions in a module that uses
Exporter and @EXPORT_OK. Then, any package that needs a function from the module can import it at will, separate from the methods in the base class.
Now, something else you need to be aware of - if you have a base class, every "sub" in that base class can be treated as a method, regardless of whether it thinks of itself as a method or not. For example:
package Functions;
use base 'Exporter';
our @EXPORT_OK = qw( func1 );
sub func1 { ... }
package Foo;
use Functions qw( func1 );
sub new { bless {}, shift }
# This is a method
sub meth1 {
my $self = shift;
...
}
package Bar;
use base 'Foo';
package main;
my $bar = Bar->new;
$bar->func1();
That
will call func1() living in the Foo package with the first argument being $bar. Try it out if you don't believe me.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.