Hi all!
I have a little problem with mutual dependency. A short example for the problem is the following:
File Hallo1.pm:
package Hallo1;
use Hallo2;
1;
File Hallo2.pm:
package Hallo2;
use Hallo1; #<<<Warning: "Compilation failed in require"
1;
In this situation, EPIC warns me at the marked line. Why?
Can anybody help me?
Regards,
Faranwannsee
PS: I'm using Eclipse 3.2.2, EPIC 0.6.17. Preferences: Enable Warnings ON / Enable taint mode OFF / Enable debugger console OFF / Suspend debugger at first statement ON / Enable Critic OFF ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It works because it forces EPIC to compile every Perl file in the project. Normally, compilation is only performed for files when they are updated, which does not take into account that other files may be also affected by changes. This is a "known problem" in EPIC, which is difficult to solve in general, but as you can see there is an easy workaround.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all!
I have a little problem with mutual dependency. A short example for the problem is the following:
File Hallo1.pm:
package Hallo1;
use Hallo2;
1;
File Hallo2.pm:
package Hallo2;
use Hallo1; #<<<Warning: "Compilation failed in require"
1;
In this situation, EPIC warns me at the marked line. Why?
Can anybody help me?
Regards,
Faranwannsee
PS: I'm using Eclipse 3.2.2, EPIC 0.6.17. Preferences: Enable Warnings ON / Enable taint mode OFF / Enable debugger console OFF / Suspend debugger at first statement ON / Enable Critic OFF ...
Have you done Project/Clean...?
Hey, it works!!! THANK YOU!! But why this works?
It works because it forces EPIC to compile every Perl file in the project. Normally, compilation is only performed for files when they are updated, which does not take into account that other files may be also affected by changes. This is a "known problem" in EPIC, which is difficult to solve in general, but as you can see there is an easy workaround.