in reply to Exporter collision detection

It does. 

>type ModA.pm
package ModA;
use Exporter qw( import );
@EXPORT = qw( foo );
sub foo { print __PACKAGE__, "\n" }
1;

>type ModB.pm
package ModB;
use Exporter qw( import );
@EXPORT = qw( foo );
sub foo { print __PACKAGE__, "\n" }
1;

>perl -we"use ModA; use ModB;"
Subroutine main::foo redefined at c:/Progs/perl5101/lib/Exporter.pm li
+ne 67.
 at -e line 1

[download]

You need to turn on warnings if you want warnings.

Replies are listed 'Best First'.
Re^2: Exporter collision detection
by Anonymous Monk on Sep 28, 2009 at 22:39 UTC
    I don't think that is good enough because it doesn't always work 
    $ perl -MData::Dump::Streamer -MYAML -wle 1

$ perl -MData::Dump::Streamer -MYAML -Wle 1
Use of uninitialized value $ENV{"B_UTILS_TRACE"} in addition (+) at /u
+sr/local/lib/perl5/site_perl/5.10.1/x86_32-linux/B/Utils.pm line 72.
Subroutine main::Dump redefined at /usr/local/lib/perl5/5.10.1/lib/Exp
+orter.pm line 67.
 at -e line 0
Name "Exporter::CARP_NOT" used only once: possible typo at /usr/local/
+lib/perl5/5.10.1/lib/Carp/Heavy.pm line 304.
Name "main::CARP_NOT" used only once: possible typo at /usr/local/lib/
+perl5/5.10.1/lib/Carp/Heavy.pm line 304.

    [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom