NAME<\/a> Exporter::Tiny::Manual::Importing \u2212 importing from Exporter::Tiny\u2212based modules<\/p>\n For the purposes of this discussion we\u2019ll assume we have a module called “MyUtils” which exports functions called “frobnicate”, “red”, “blue”, and “green”. It has a tag set up called “:colours” which corresponds to “red”, “blue”, and “green”.<\/p>\n Many of these tricks may seem familiar from Sub::Exporter. That is intentional. Exporter::Tiny doesn\u2019t attempt to provide every feature of Sub::Exporter, but where it does it usually uses a fairly similar API.<\/small><\/p>\n Basic importing<\/b> use MyUtils “frobnicate”;<\/p>\n Or a list of functions:<\/p>\n use MyUtils “red”, “green”;<\/p>\n Perl\u2019s “qw()” shorthand for a list of words is pretty useful:<\/p>\n use MyUtils qw( red green );<\/p>\n If the module defines tags, you can import them like this:<\/p>\n use MyUtils qw( :colours );<\/p>\n Or with a hyphen instead of a colon:<\/p>\n use MyUtils qw( \u2212colours );<\/p>\n Hyphens are good because Perl will autoquote a bareword that follows them:<\/p>\n use MyUtils \u2212colours;<\/p>\n And it\u2019s possible to mix function names and tags in the same list:<\/p>\n use MyUtils qw( frobnicate :colours );<\/p>\n Renaming imported functions<\/b> use MyUtils “frobnicate” => { \u2212as => “frob” };<\/p>\n Or you can apply a prefix and\/or suffix. The following imports the function and calls it “my_frobinate_thing”.<\/p>\n use MyUtils “frobnicate” => { \u2212prefix => “my_”, \u2212suffix => “_thing” };<\/p>\n You can apply a prefix\/suffix to all<\/b> functions you import by placing the hashref first<\/b> in the import list. (This first hashref is referred to as the global options hash, and can do some special things.)<\/p>\n use MyUtils { prefix => “my_” }, “frobnicate”;<\/p>\n Did you notice that we used “\u2212prefix” and “\u2212suffix” in the normal options hash, but “prefix” and “suffix” (no hyphen) in the global options hash? That\u2019s a common pattern with this module.<\/p>\n You can import the same function multiple times with different names:<\/p>\n use MyUtils Tags can take the “\u2212prefix” and “\u2212suffix” options too. The following imports “colour_red”, “colour_green”, and “colour_blue”:<\/p>\n use MyUtils \u2212colours => { \u2212prefix => “colour_” };<\/p>\n You can also set “\u2212as” to be a coderef to generate a function name. This imports functions called “RED”, “GREEN”, and “BLUE”:<\/p>\n use MyUtils \u2212colours => { \u2212as => sub { uc($_[0]) } };<\/p>\n Note that it doesn\u2019t make sense to use “\u2212as” with a tag unless you\u2019re doing this coderef thing. Coderef “as” also works in the global options hash.<\/p>\n DO NOT WANT<\/small> !<\/b> use MyUtils qw( \u2212all !frobnicate );<\/p>\n You can add the bang prefix to tags too. This will import everything except the colours.<\/p>\n use MyUtils qw( \u2212all !:colours );<\/p>\n Negated imports always “win”, so the following will not import “frobnicate”, no matter how many times you repeat it…<\/p>\n use MyUtils qw( !frobnicate frobnicate frobnicate frobnicate );<\/p>\n Importing by regexp<\/b> use MyUtils qw( \/^F\/i );<\/p>\n Or import everything except functions beginning with a “z”:<\/p>\n use MyUtils qw( \u2212all !\/^Z\/i );<\/p>\n Note that regexps are always supplied as strings<\/i> starting with “\/”, and not as quoted regexp references (“qr\/…\/”).<\/p>\n Import functions into another package<\/b> use MyUtils { into => “OtherPkg” }, “frobnicate”; However, Import::Into will probably provide you with a better approach which doesn\u2019t just work with Exporter::Tiny, but all<\/b> exporters.<\/p>\n Lexical subs<\/b> There is this Sub::Exporter::Lexical thing that was designed as a plugin for Sub::Exporter, but Exporter::Tiny\u2019s API<\/small> is close enough that it will work. Do you remember that global options hash? Just use that to tell Exporter::Tiny to use an alternative sub installer.<\/p>\n { Another way to do lexical functions is to import a function into a scalar variable:<\/p>\n my $func; You can even provide a hashref to put all imported functions into as part of that global options hash I mentioned earlier.<\/p>\n my %funcs; Unimporting<\/b> no MyUtils;<\/p>\n Or just specific ones:<\/p>\n no MyUtils qw(frobnicate);<\/p>\n If you renamed a function when you imported it, you should unimport by the new name:<\/p>\n use MyUtils frobnicate => { \u2212as => “frob” }; Unimporting using tags and regexps should mostly do what you want.<\/p>\n Overwriting existing sub \u2019%s::%s\u2019 with sub \u2019%s\u2019 exported by %s<\/b><\/p>\n A warning issued if Exporter::Tiny is asked to export a symbol which will result in an existing sub being overwritten. This warning can be suppressed using either of the following:<\/p>\n use MyUtils { replace => 1 }, “frobnicate”; Or can be upgraded to a fatal error:<\/p>\n use MyUtils { replace => “die” }, “frobnicate”; Refusing to overwrite existing sub \u2019%s::%s\u2019 with sub \u2019%s\u2019 exported by The fatal version of the above warning.<\/p>\n Could not find sub \u2019%s\u2019 exported by %s<\/b><\/p>\n You requested to import a sub which the package does not provide.<\/p>\n Cannot provide an \u2212as option for tags<\/b><\/p>\n Because a tag may provide more than one function, it does not make sense to request a single name for it. Instead use “\u2212prefix” or “\u2212suffix”.<\/p>\n Passing options to unimport \u2019%s\u2019 makes no sense<\/b><\/p>\n When you import a sub, it occasionally makes sense to pass some options for it. However, when unimporting, options do nothing, so this warning is issued.<\/p>\n Exporter::Shiny, Exporter::Tiny.<\/p>\n Toby Inkster This software is copyright (c) 2013\u22122014, 2017 by Toby Inkster.<\/p>\n This is free software; you can redistribute it and\/or modify it under the same terms as the Perl 5 programming language system itself.<\/p>\n THIS PACKAGE IS PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.<\/small><\/p>\n Exporter::Tiny::Manual::Importing \u2212 importing from Exporter::Tiny\u2212based modules <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[3154,3007],"class_list":["post-6783","post","type-post","status-publish","format-standard","hentry","category-sin-categoria","tag-exportertinymanualimporting","tag-man3"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6783","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=6783"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/6783\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=6783"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=6783"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=6783"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
DESCRIPTION<\/a>
DIAGNOSTICS<\/a>
SEE ALSO<\/a>
AUTHOR<\/a>
COPYRIGHT AND LICENCE<\/a>
DISCLAIMER OF WARRANTIES<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
It\u2019s easy to import a single function from a module:<\/p>\n
It\u2019s possible to rename a function you\u2019re importing:<\/p>\n
“frobnicate” => { \u2212as => “frob” },
“frobnicate” => { \u2212as => “frbnct” };<\/p>\n
Sometimes you want to supply a list of functions you don\u2019t<\/b> want to import. To do that, prefix the function with a bang. This imports everything except “frobnicate”:<\/p>\n
Here\u2019s how you could import all functions beginning with an “f”:<\/p>\n
Occasionally you need to import functions not into your own package, but into a different package. You can do that like this:<\/p>\n
OtherPkg::frobincate(…);<\/p>\n
Often you want to make use of an exported function, but don\u2019t want it to “pollute” your namespace.<\/p>\n
use Sub::Exporter::Lexical lexical_installer => { \u2212as => “lex” };
use MyUtils { installer => lex }, “frobnicate”;
frobnicate(…); # ok
}
frobnicate(…); # not ok<\/p>\n
use MyUtils “frobnicate” => { \u2212as => $func };
$func\u2212>(…);<\/p>\n
use MyUtils { into => %funcs }, “frobnicate”;
$funcs{frobnicate}\u2212>(…);<\/p>\n
You can unimport the functions that MyUtils added to your namespace:<\/p>\n
…;
no MyUtils “frob”;<\/p>\nDIAGNOSTICS <\/a> <\/h2>\n
use MyUtils “frobnicate” => { \u2212replace => 1 };<\/p>\n
use MyUtils “frobnicate” => { \u2212replace => “die” };<\/p>\n
%s<\/b><\/p>\nSEE ALSO <\/a> <\/h2>\n
AUTHOR <\/a> <\/h2>\n
COPYRIGHT AND LICENCE <\/a> <\/h2>\n
DISCLAIMER OF WARRANTIES <\/a> <\/h2>\n
\n","protected":false},"excerpt":{"rendered":"