Well, use eval(). For example, for my HTTP-Daemon I need to redefine a socket method that make impossible to share the same socket port with multiple childs on Win32, so I use this:
# Fix a bug on sockname of IO::Socket, that block the app for multi ch
+ilds with
# the same server opened. Or for a GLOB blessed in a package different
+ than
# IO::Socket, since the socket of the server is blessed to HTTP::Daemo
+n! (Bug saw only on Win32).
if ( $^O =~ /(?:^ms|win|dos)/i ) {
eval(q`
package HTTP::Daemon ;
sub sockname {
#getsockname($_[0]);
getsockname( fileno($_[0]) );
}
`);
}
But I think that the best option is to extend the class (like
robartes said), since this doesn't change the method for all the mod_perl scripts (let's say that you run different scripts inside mod_perl):
package Apache::FakeRequest::ViceRaid;
use base qw(Apache::FakeRequest);
sub lookup_uri { ... }
Graciliano M. P.
"The creativity is the expression of the liberty".
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.