Re: What happens when you load the same module twice?

In the specific degenerate case given Perl does load the code twice. So it sees the code twice and complains that the Package::rout is defined twice. The exporting and importing of names is not germaine to the warning. People and Perl are being confused by OS limitations.

Be well,
rir

--
Here's a nickel, kid, get yourself a real filesystem. And keep the change.

Comment on Re: What happens when you load the same module twice? Download Code

Replies are listed 'Best First'.
Re^2: What happens when you load the same module twice? by dragonchild (Archbishop) on Feb 10, 2005 at 19:44 UTC
The fact that you're referring to Win32 (and VMS) as a degenerate case is absolutely delicious. ++! Being right, does not endow the right to be rude; politeness costs nothing. Being unknowing, is not the same as being stupid. Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence. Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.	[reply]

Replies are listed 'Best First'.

Re^2: What happens when you load the same module twice?
by dragonchild (Archbishop) on Feb 10, 2005 at 19:44 UTC

degenerate case

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

[reply]