For those who were interested in the problem, I was able to have the "new" code run in a "safe" way by forking... forking copies the symbol table and changes to it in the child process are not mirrored to the parent process.
Here's a quick snippet showing the method...
use Data::Dumper; sub foo { if ( open(FROM, "-|" ) ) { # PARENT local($/); my $output = <FROM>; # from the child my $retval = eval "$output"; my @values = @$retval; return $values[0] if( @values == 1 ); return @values; } else { # CHILD unshift( @INC, "/path/to/NEW"); findAndRequire( 'My::Package' ); my @output = My::Package::func(); # local not really needed here, but who is counting local $Data::Dumper::Purity = 1; local $Data::Dumper::Terse = 1; print Dumper( \@output ); # to the parent exit; } } sub findAndRequire { my ($pkgName) = @_; $pkgName =~ s/::/\//g; # search @INC for a file which matches foreach my $dir (@INC) { my $file = "${dir}/${pkgName}.pm"; if( -e $file ) { require "$file"; last; } } } # Call our "proxied" function! my $output = foo(); local $Data::Dumper::Purity = 1; local $Data::Dumper::Terse = 1; print "OUTPUT = " . Dumper( $output );

In reply to Re: How can I (safely) use packages of the same name but different versions? by xevian
in thread How can I (safely) use packages of the same name but different versions? by xevian

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.