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.
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.