I had the impression from reading your node that the option to import the import function wasn't so much a significant change to Exporter.pm as much as it was a happy coincidence that importing the import function worked correctly instead of using inheritance. I also didn't have much reason to re-read Exporter's documentation since the API hadn't changed in any way.
What originally wrote didn't look correct and it only now occurrs to me that this form of importing wouldn't normally work because import is always called as a class method anyway. In a more normal module, what you wrote would be flat-out incorrect code. Thinks would still work if you did this in normal code but I've never seen anyone seriously advocate for flattening inheritance trees to avoid recursive @ISA lookups in this particular way.
Which version is *import = \ &Exporter::import kosher in anyway? I didn't see a mention of this use of the API in even the 5.8.5 documentation on search.cpan.org.
In reply to Re^5: Problem with "use Exporter qw(import);"
by diotalevi
in thread Problem with "use Exporter qw(import);"
by johnnywang
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |