Our shop has a lot of legacy code that uses Exporter and relies more on @EXPORT than @EXPORT_OK. So a program that uses a few inhouse modules may well have had a noiseless name space collision ie (more than one module exports the same name).
Since I was a nice boy, Santa brought me something to play with - Exporter. Tinkering resulted in a modified Exporter.pm and Exporter::Heavy.pm. In Exporter::Heavy the modified sub heavy_export preserves $callpkg, $pkg and $sym in the hash ref $Exporter::Exported. In Exporter a new INIT block checks the symbols in each in-house script/module to see if they were "exported" more than once before terminating.
Putting Exporter.pm and Exporter::Heavy.pm into a local library allowed me do "perl -I<locallib> <script/module>" ie use this modified exporter.
C:\Exporter>perl -I. test_03.pl
Subroutine jkl redefined at test_03.pl line 16.
Exports list has been generated. Exporter will now terminate.
which claims that "main" defined a sub "abc" which was replaced by the "abc" exported by "One". The "def" exported by "One" was replaced by the "def" exported by "Two", etc. (Far more things are exported but we're only interested in the potential collisions.)
Would these changes be considered useful enhancements or ?