📄 exporter.pm
字号:
package Exporter;require 5.001;$ExportLevel = 0;$Verbose ||= 0;$VERSION = '5.562';sub export_to_level { require Exporter::Heavy; goto &heavy_export_to_level;}sub export { require Exporter::Heavy; goto &heavy_export;}sub export_tags { require Exporter::Heavy; _push_tags((caller)[0], "EXPORT", \@_);}sub export_ok_tags { require Exporter::Heavy; _push_tags((caller)[0], "EXPORT_OK", \@_);}sub import { my $pkg = shift; my $callpkg = caller($ExportLevel); *exports = *{"$pkg\::EXPORT"}; # We *need* to treat @{"$pkg\::EXPORT_FAIL"} since Carp uses it :-( *fail = *{"$pkg\::EXPORT_FAIL"}; return export $pkg, $callpkg, @_ if $Verbose or $Debug or @fail > 1; my $args = @_ or @_ = @exports; if ($args and not %exports) { foreach my $sym (@exports, @{"$pkg\::EXPORT_OK"}) { $sym =~ s/^&//; $exports{$sym} = 1; } } if ($Verbose or $Debug or grep {/\W/ or $args and not exists $exports{$_} or @fail and $_ eq $fail[0] or (@{"$pkg\::EXPORT_OK"} and $_ eq ${"$pkg\::EXPORT_OK"}[0])} @_) { return export $pkg, $callpkg, ($args ? @_ : ()); } #local $SIG{__WARN__} = sub {require Carp; goto &Carp::carp}; local $SIG{__WARN__} = sub {require Carp; local $Carp::CarpLevel = 1; &Carp::carp}; foreach $sym (@_) { # shortcut for the common case of no type character *{"$callpkg\::$sym"} = \&{"$pkg\::$sym"}; }}1;# A simple self test harness. Change 'require Carp' to 'use Carp ()' for testing.# package main; eval(join('',<DATA>)) or die $@ unless caller;__END__package Test;$INC{'Exporter.pm'} = 1;@ISA = qw(Exporter);@EXPORT = qw(A1 A2 A3 A4 A5);@EXPORT_OK = qw(B1 B2 B3 B4 B5);%EXPORT_TAGS = (T1=>[qw(A1 A2 B1 B2)], T2=>[qw(A1 A2 B3 B4)], T3=>[qw(X3)]);@EXPORT_FAIL = qw(B4);Exporter::export_ok_tags('T3', 'unknown_tag');sub export_fail { map { "Test::$_" } @_ # edit symbols just as an example}package main;$Exporter::Verbose = 1;#import Test;#import Test qw(X3); # export ok via export_ok_tags()#import Test qw(:T1 !A2 /5/ !/3/ B5);import Test qw(:T2 !B4);import Test qw(:T2); # should fail1;=head1 NAMEExporter - Implements default import method for modules=head1 SYNOPSISIn module ModuleName.pm: package ModuleName; require Exporter; @ISA = qw(Exporter); @EXPORT = qw(...); # symbols to export by default @EXPORT_OK = qw(...); # symbols to export on request %EXPORT_TAGS = tag => [...]; # define names for sets of symbolsIn other files which wish to use ModuleName: use ModuleName; # import default symbols into my package use ModuleName qw(...); # import listed symbols into my package use ModuleName (); # do not import any symbols=head1 DESCRIPTIONThe Exporter module implements a default C<import> method whichmany modules choose to inherit rather than implement their own.Perl automatically calls the C<import> method when processing aC<use> statement for a module. Modules and C<use> are documentedin L<perlfunc> and L<perlmod>. Understanding the concept ofmodules and how the C<use> statement operates is important tounderstanding the Exporter.=head2 How to ExportThe arrays C<@EXPORT> and C<@EXPORT_OK> in a module hold lists ofsymbols that are going to be exported into the users name space bydefault, or which they can request to be exported, respectively. Thesymbols can represent functions, scalars, arrays, hashes, or typeglobs.The symbols must be given by full name with the exception that theampersand in front of a function is optional, e.g. @EXPORT = qw(afunc $scalar @array); # afunc is a function @EXPORT_OK = qw(&bfunc %hash *typeglob); # explicit prefix on &bfunc=head2 Selecting What To ExportDo B<not> export method names!Do B<not> export anything else by default without a good reason!Exports pollute the namespace of the module user. If you must exporttry to use @EXPORT_OK in preference to @EXPORT and avoid short orcommon symbol names to reduce the risk of name clashes.Generally anything not exported is still accessible from outside themodule using the ModuleName::item_name (or $blessed_ref-E<gt>method)syntax. By convention you can use a leading underscore on names toinformally indicate that they are 'internal' and not for public use.(It is actually possible to get private functions by saying: my $subref = sub { ... }; &$subref;But there's no way to call that directly as a method, since a methodmust have a name in the symbol table.)As a general rule, if the module is trying to be object orientedthen export nothing. If it's just a collection of functions then@EXPORT_OK anything but use @EXPORT with caution.Other module design guidelines can be found in L<perlmod>.=head2 Specialised Import ListsIf the first entry in an import list begins with !, : or / then thelist is treated as a series of specifications which either add to ordelete from the list of names to import. They are processed left toright. Specifications are in the form: [!]name This name only [!]:DEFAULT All names in @EXPORT [!]:tag All names in $EXPORT_TAGS{tag} anonymous list [!]/pattern/ All names in @EXPORT and @EXPORT_OK which matchA leading ! indicates that matching names should be deleted from thelist of names to import. If the first specification is a deletion itis treated as though preceded by :DEFAULT. If you just want to importextra names in addition to the default set you will still need toinclude :DEFAULT explicitly.e.g., Module.pm defines: @EXPORT = qw(A1 A2 A3 A4 A5); @EXPORT_OK = qw(B1 B2 B3 B4 B5); %EXPORT_TAGS = (T1 => [qw(A1 A2 B1 B2)], T2 => [qw(A1 A2 B3 B4)]); Note that you cannot use tags in @EXPORT or @EXPORT_OK. Names in EXPORT_TAGS must also appear in @EXPORT or @EXPORT_OK.An application using Module can say something like: use Module qw(:DEFAULT :T2 !B3 A3);Other examples include: use Socket qw(!/^[AP]F_/ !SOMAXCONN !SOL_SOCKET); use POSIX qw(:errno_h :termios_h !TCSADRAIN !/^EXIT/);Remember that most patterns (using //) will need to be anchoredwith a leading ^, e.g., C</^EXIT/> rather than C</EXIT/>.You can say C<BEGIN { $Exporter::Verbose=1 }> to see how thespecifications are being processed and what is actually being importedinto modules.=head2 Exporting without using Export's import methodExporter has a special method, 'export_to_level' which is used in situationswhere you can't directly call Export's import method. The export_to_levelmethod looks like:MyPackage->export_to_level($where_to_export, $package, @what_to_export);where $where_to_export is an integer telling how far up the calling stackto export your symbols, and @what_to_export is an array telling whatsymbols *to* export (usually this is @_). The $package argument iscurrently unused.For example, suppose that you have a module, A, which already has animport function:package A;@ISA = qw(Exporter);@EXPORT_OK = qw ($b);sub import{ $A::b = 1; # not a very useful import method}and you want to Export symbol $A::b back to the module that called package A. Since Exporter relies on the import method to work, via inheritance, as it stands Exporter::import() will never get called. Instead, say the following:package A;@ISA = qw(Exporter);@EXPORT_OK = qw ($b);sub import{ $A::b = 1; A->export_to_level(1, @_);}This will export the symbols one level 'above' the current package - ie: to the program or module that used package A. Note: Be careful not to modify '@_' at all before you call export_to_level- or people using your package will get very unexplained results!=head2 Module Version CheckingThe Exporter module will convert an attempt to import a number from amodule into a call to $module_name-E<gt>require_version($value). This canbe used to validate that the version of the module being used isgreater than or equal to the required version.The Exporter module supplies a default require_version method whichchecks the value of $VERSION in the exporting module.Since the default require_version method treats the $VERSION number asa simple numeric value it will regard version 1.10 as lower than1.9. For this reason it is strongly recommended that you use numberswith at least two decimal places, e.g., 1.09.=head2 Managing Unknown SymbolsIn some situations you may want to prevent certain symbols from beingexported. Typically this applies to extensions which have functionsor constants that may not exist on some systems.The names of any symbols that cannot be exported should be listedin the C<@EXPORT_FAIL> array.If a module attempts to import any of these symbols the Exporterwill give the module an opportunity to handle the situation beforegenerating an error. The Exporter will call an export_fail methodwith a list of the failed symbols: @failed_symbols = $module_name->export_fail(@failed_symbols);If the export_fail method returns an empty list then no error isrecorded and all the requested symbols are exported. If the returnedlist is not empty then an error is generated for each symbol and theexport fails. The Exporter provides a default export_fail method whichsimply returns the list unchanged.Uses for the export_fail method include giving better error messagesfor some symbols and performing lazy architectural checks (put moresymbols into @EXPORT_FAIL by default and then take them out if someoneactually tries to use them and an expensive check shows that they areusable on that platform).=head2 Tag Handling Utility FunctionsSince the symbols listed within %EXPORT_TAGS must also appear in either@EXPORT or @EXPORT_OK, two utility functions are provided which allowyou to easily add tagged sets of symbols to @EXPORT or @EXPORT_OK: %EXPORT_TAGS = (foo => [qw(aa bb cc)], bar => [qw(aa cc dd)]); Exporter::export_tags('foo'); # add aa, bb and cc to @EXPORT Exporter::export_ok_tags('bar'); # add aa, cc and dd to @EXPORT_OKAny names which are not tags are added to @EXPORT or @EXPORT_OKunchanged but will trigger a warning (with C<-w>) to avoid misspelt tagsnames being silently added to @EXPORT or @EXPORT_OK. Future versionsmay make this a fatal error.=cut
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -