|Think about Loose Coupling|
attempt to reload My_module.pm abortedby prashanttekriwal (Novice)
|on Apr 18, 2013 at 12:44 UTC||Need Help??|
prashanttekriwal has asked for the
wisdom of the Perl Monks concerning the following question:
First of all let me give you a little background of what we are doing and then I will explain the issue and the solution I need.----Background----
Our team owns a test automation framework that enables users to develop and execute their tests.
Till now the whole system and the users are using perl 5.8.8 and hence we decided to migrate to perl 5.14.0.----Issue----
Now, one of the user is getting an error when running his scripts using perl 5.14 which is working fine with perl5.8.8.
The error coming is 'Attempt to reload <module> aborted', where <module> is an internal module of our company.
I know the background of the error but we don't know where previous load of this module is failing since the test script has a long list of module reference.----What I need----
To me the issue is not where the previous load is failing since it was failing earlier as well (with perl 5.8.8) but the test script was still going through.
I need to know, is there a way to tell perl5.14.0 not to treat this as an error (like perl5.8.8 does).
We can't put the code block where its failing under 'eval' as its doing 'use <module>' right at the beginning of the file.
Any help, solution, workaround for this issue will be highly appreciated.Thanks in Advance,