Tom Allison am Donnerstag, 13. Oktober 2005 12.52: > I'm pretty sure I'm not doing this right. > > I have two modules of the same name, current version and future version, > in two different directories. > > $HOME/test/Module1.pm > $HOME/test/Module2.pm > $HOME/lib/Module1.pm > $HOME/lib/Module2.pm > > and another module: $HOME/lib/Module3.pm > > Under perl -d I can't seem to ignore the current versions > $HOME/lib/Module1.pm > $HOME/lib/Module2.pm > and see only the future version. > > I can get part of the way there, but right now the modules in my test > directory have a call for "use lib '/home/tallison/lib'" that seems to > throw things a bit. But I need that in order for Module3 to be available. > > I've tried creating a shell script where I export a PERL5LIB with no > reference to my $HOME/lib directory and that doesn't work. It still > finds the wrong module. > > the option -M-lib doesn't seem to have any effect on this either. > > grr... I'm trying to do this the best way possible so that I can have > real test scripts that do real tests without breaking everything under > the sun.
I don't quite understand what your problem is, but maybe it is relevant for you that the modules are found and used in the order in which they are specified in @INC (which is manipulated by 'use lib'). F.e. if $HOME/test is before $HOME/lib in @INC, the test modules are used. joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
