comment on

Ok, here it is the full solution using an in-memory file:

use strict;
use warnings;
use Path::Tiny;

sub hotpatch {
    my ($self, $module) = @_;
    if ($module eq 'AnyEvent/DNS.pm') {
        for my $inc (@INC) {
            next if ref $inc;
            if (open my $in, '<', path($inc)->child($module)) {
                my $buffer = do { undef $/; <$in> };
                $buffer =~ s/\bsub\s+DOMAIN_PORT\b/sub DOMAIN_PORT () 
+{ 1053 } sub FORMER_DOMAIN_PORT/;
                open my $out, '<', \$buffer
                    or die "Couldn't patch AnyEvent::DNS; your Perl do
+es not support in-memory filehandles";
                return $out;
            }
        }
        warn "couldn't patch AnyEvent::DNS";
    }
    return undef;
}

BEGIN { unshift @INC, \&hotpatch }

use AnyEvent::DNS;

BEGIN { @INC = grep not(ref and $_ eq \&hotpatch), @INC }

say AnyEvent::DNS::DOMAIN_PORT();
say AnyEvent::DNS::FORMER_DOMAIN_PORT();
[download]

In reply to Re^4: How to redefine a modules private function? by salva
in thread How to redefine a modules private function? by sectokia

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.


XP is just a number
	PerlMonks