use Thing1 ();
use Thing2 ();
+ use Thing3 ();
sub import {
my $target = caller;
Thing1->import::into($target);
Thing2->import::into($target, qw(import arguments));
+ Thing3->import::into(1); # import to level
}
Note: you don't need to do anything more clever than this provided you
package (and in fact on any object as well, although it's rarer that you'd
want to do that).
+If you provide C<import::into> with an integer instead of a package name, it
+will be used as the number of stack frames to skip to find where to export to.
+This has the advantage of preserving the apparent filename and line number
+being exported to, which some modules (L<autodie>, L<strictures>) check.
+
Finally, we also provide an C<unimport::out_of> to allow the exporting of the
effect of C<no>:
these approaches alone on something like L<Moose> or L<Moo> that's both
an exporter and a pragma.
-So, the complete solution is:
+So, a solution for that is:
my $sub = eval "package $target; sub { shift->import(\@_) }";
$sub->($thing, @import_args);
effect, and from the right package for caller checking to work - and so
behaves correctly for all types of exporter, for pragmas, and for hybrids.
+Additionally, some import routines check the filename they are being imported
+to. This can be dealt with by generating a L<#line directive|perlsyn/Plain
+Old Comments (Not!)> in the eval, which will change what C<caller> reports for
+the filename when called in the importer. The filename and line number to use
+in the directive then need to be fetched using C<caller>:
+
+ my ($target, $file, $line) = caller(1);
+ my $sub = eval qq{
+ package $target;
+ #line $line "$file"
+ sub { shift->import(\@_) }
+ };
+ $sub->($thing, @import_args);
+
Remembering all this, however, is excessively irritating. So I wrote a module
so I didn't have to anymore. Loading L<Import::Into> creates a global method
C<import::into> which you can call on any package to import it into another