According to Exporter latest docs
(http://search.cpan.org/~ferreira/Exporter-5.62c/lib/Exporter.pm#Exporting_without_inheriting_from_Exporter),
use Exporter 'import';
has been introduced in version 5.57 of Exporter, released with perl
5.8.3. Thus,
BEGIN {
require Exporter;
*{import} = \&Exporter::import;
}
would be justifiable if M::B does not intend to force an Exporter
upgrade (since it has dual life now). From the list of changes of
lib/Exporter.pm, including:
(from http://public.activestate.com/cgi-bin/perlbrowse/l/lib/Exporter.pm)
21798 on 2003/11/28 by [EMAIL PROTECTED]
Implement C<use Exporter 'import'> :
Subject: Re: [PATCH] Exporter-related PODs
From: Fergal Daly <[EMAIL PROTECTED]>
Date: Mon, 10 Nov 2003 00:08:52 +0000
Message-Id: <[EMAIL PROTECTED]>
(tweaked, so the imported import() doesn't spit out warnings)
it seems that the ugly idiom should (hopefully) work alright for older
Exporter's.
Regards,
Adriano Ferreira
On Feb 17, 2008 3:05 AM, Ken Williams <[EMAIL PROTECTED]> wrote:
> On Feb 16, 2008 11:51 PM, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
> > Looks like we need to roll this back to be compatible with 5.6.2. Are
> > we trying to be compatible with 5.6.2?
>
> Yeah, I guess we are. Thanks for the spot.
>
> -Ken
>
