Re^17: global var

This is how you write that shorter and better

use WHATEVER(); ## no imports, repeat for all failing modules
BEGIN{warn join "\n" , %INC, " " } ## log which files were loaded
[download]

Comment on Re^17: global var Download Code

Replies are listed 'Best First'.
Re^18: global var by huck (Prior) on Apr 11, 2017 at 21:51 UTC
No it isnt, notice i didnt stop when i found it, like use/require does.	[reply]
Re^19: global var by Anonymous Monk on Apr 11, 2017 at 22:33 UTC
No it isnt, notice i didnt stop when i found it, like use/require does. Why is that important? use/require only load one file	[reply]
Re^20: global var by huck (Prior) on Apr 11, 2017 at 22:59 UTC
use/require only load one file yes of course What if there are two files named the same in the lib stack. why does it seem to work sometimes and not others, could it be one loads it from one place and the second loads it from another. If the faulty module existed higher in the lib stack in the failing code then that code would fail, but if in the working code the good module came before the faulty one in the lib stack it would get loaded instead and that code works. That is why i wanted to see where ALL of the manageusers.pm files were located. He may think he has the right lib added to the stack, but it is in the wrong position. But for the faulty code it looks like it only found one copy.	[reply]
Re^21: global var by Anonymous Monk on Apr 12, 2017 at 00:06 UTC
Re^22: global var by huck (Prior) on Apr 12, 2017 at 00:39 UTC
Some notes below your chosen depth have not been shown here