If you want to re-define a subroutine in a module to suit your needs, consider either creating a descendant class or use eval to re-define the subroutine:
package MyClass2;
use MyClass;
use Exporter;
@ISA = ('MyClass');
@EXPORT = @MyClass2::EXPORT;
sub overridden {
print "This is *my* method, overriding MyClass::overridden!\n";
}
Or:
#!/usr/bin/perl
use MyClass;
sub MyClass::overridden {
print "I need this to behave differently.\n";
}
Or:
#!/usr/bin/perl
use MyClass;
my $code = get_some_code_text;
eval "sub MyClass::overridden { $code }";
Using eval in this way lets you completely re-define your functions internally, even stuff in other modules, without needing to write your changes in a new file and then "re-use" (re-execute) that file to get your changes to take effect. Persistency might be a good reason to want to edit the source directly, though, so I understand that.
-
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.
|