📄 selfloader.pm
字号:
package SelfLoader;use 5.009005; # due to new regexp featuresuse strict;use Exporter;our @ISA = qw(Exporter);our @EXPORT = qw(AUTOLOAD);our $VERSION = "1.11";sub Version {$VERSION}sub DEBUG () { 0 }my %Cache; # private cache for all SelfLoader's client packages# allow checking for valid ': attrlist' attachments# see also AutoSplitmy $attr_list = qr{ \s* : \s* (?: # one attribute (?> # no backtrack (?! \d) \w+ (?<nested> \( (?: [^()]++ | (?&nested)++ )*+ \) ) ? ) (?: \s* : \s* | \s+ (?! :) ) )*}x;# in croak and carp, protect $@ from "require Carp;" RT #40216sub croak { { local $@; require Carp; } goto &Carp::croak }sub carp { { local $@; require Carp; } goto &Carp::carp }AUTOLOAD { our $AUTOLOAD; print STDERR "SelfLoader::AUTOLOAD for $AUTOLOAD\n" if DEBUG; my $SL_code = $Cache{$AUTOLOAD}; my $save = $@; # evals in both AUTOLOAD and _load_stubs can corrupt $@ unless ($SL_code) { # Maybe this pack had stubs before __DATA__, and never initialized. # Or, this maybe an automatic DESTROY method call when none exists. $AUTOLOAD =~ m/^(.*)::/; SelfLoader->_load_stubs($1) unless exists $Cache{"${1}::<DATA"}; $SL_code = $Cache{$AUTOLOAD}; $SL_code = "sub $AUTOLOAD { }" if (!$SL_code and $AUTOLOAD =~ m/::DESTROY$/); croak "Undefined subroutine $AUTOLOAD" unless $SL_code; } print STDERR "SelfLoader::AUTOLOAD eval: $SL_code\n" if DEBUG; { no strict; eval $SL_code; } if ($@) { $@ =~ s/ at .*\n//; croak $@; } $@ = $save; defined(&$AUTOLOAD) || die "SelfLoader inconsistency error"; delete $Cache{$AUTOLOAD}; goto &$AUTOLOAD}sub load_stubs { shift->_load_stubs((caller)[0]) }sub _load_stubs { # $endlines is used by Devel::SelfStubber to capture lines after __END__ my($self, $callpack, $endlines) = @_; no strict "refs"; my $fh = \*{"${callpack}::DATA"}; use strict; my $currpack = $callpack; my($line,$name,@lines, @stubs, $protoype); print STDERR "SelfLoader::load_stubs($callpack)\n" if DEBUG; croak("$callpack doesn't contain an __DATA__ token") unless defined fileno($fh); # Protect: fork() shares the file pointer between the parent and the kid if(sysseek($fh, tell($fh), 0)) { open my $nfh, '<&', $fh or croak "reopen: $!";# dup() the fd close $fh or die "close: $1"; # autocloses, but be paranoid open $fh, '<&', $nfh or croak "reopen2: $!"; # dup() the fd "back" close $nfh or die "close after reopen: $1"; # autocloses, but be paranoid } $Cache{"${currpack}::<DATA"} = 1; # indicate package is cached local($/) = "\n"; while(defined($line = <$fh>) and $line !~ m/^__END__/) { if ($line =~ m/^sub\s+([\w:]+)\s*((?:\([\\\$\@\%\&\*\;]*\))?(?:$attr_list)?)/) { push(@stubs, $self->_add_to_cache($name, $currpack, \@lines, $protoype)); $protoype = $2; @lines = ($line); if (index($1,'::') == -1) { # simple sub name $name = "${currpack}::$1"; } else { # sub name with package $name = $1; $name =~ m/^(.*)::/; if (defined(&{"${1}::AUTOLOAD"})) { \&{"${1}::AUTOLOAD"} == \&SelfLoader::AUTOLOAD || die 'SelfLoader Error: attempt to specify Selfloading', " sub $name in non-selfloading module $1"; } else { $self->export($1,'AUTOLOAD'); } } } elsif ($line =~ m/^package\s+([\w:]+)/) { # A package declared push(@stubs, $self->_add_to_cache($name, $currpack, \@lines, $protoype)); $self->_package_defined($line); $name = ''; @lines = (); $currpack = $1; $Cache{"${currpack}::<DATA"} = 1; # indicate package is cached if (defined(&{"${1}::AUTOLOAD"})) { \&{"${1}::AUTOLOAD"} == \&SelfLoader::AUTOLOAD || die 'SelfLoader Error: attempt to specify Selfloading', " package $currpack which already has AUTOLOAD"; } else { $self->export($currpack,'AUTOLOAD'); } } else { push(@lines,$line); } } if (defined($line) && $line =~ /^__END__/) { # __END__ unless ($line =~ /^__END__\s*DATA/) { if ($endlines) { # Devel::SelfStubber would like us to capture the lines after # __END__ so it can write out the entire file @$endlines = <$fh>; } close($fh); } } push(@stubs, $self->_add_to_cache($name, $currpack, \@lines, $protoype)); no strict; eval join('', @stubs) if @stubs;}sub _add_to_cache { my($self,$fullname,$pack,$lines, $protoype) = @_; return () unless $fullname; carp("Redefining sub $fullname") if exists $Cache{$fullname}; $Cache{$fullname} = join('', "package $pack; ",@$lines); print STDERR "SelfLoader cached $fullname: $Cache{$fullname}" if DEBUG; # return stub to be eval'd defined($protoype) ? "sub $fullname $protoype;" : "sub $fullname;"}sub _package_defined {}1;__END__=head1 NAMESelfLoader - load functions only on demand=head1 SYNOPSIS package FOOBAR; use SelfLoader; ... (initializing code) __DATA__ sub {....=head1 DESCRIPTIONThis module tells its users that functions in the FOOBAR package are to beautoloaded from after the C<__DATA__> token. See alsoL<perlsub/"Autoloading">.=head2 The __DATA__ tokenThe C<__DATA__> token tells the perl compiler that the perl codefor compilation is finished. Everything after the C<__DATA__> tokenis available for reading via the filehandle FOOBAR::DATA,where FOOBAR is the name of the current package when the C<__DATA__>token is reached. This works just the same as C<__END__> does inpackage 'main', but for other modules data after C<__END__> is notautomatically retrievable, whereas data after C<__DATA__> is.The C<__DATA__> token is not recognized in versions of perl prior to5.001m.Note that it is possible to have C<__DATA__> tokens in the same packagein multiple files, and that the last C<__DATA__> token in a givenpackage that is encountered by the compiler is the one accessibleby the filehandle. This also applies to C<__END__> and main, i.e. ifthe 'main' program has an C<__END__>, but a module 'require'd (_not_ 'use'd)by that program has a 'package main;' declaration followed by an 'C<__DATA__>',then the C<DATA> filehandle is set to access the data after the C<__DATA__>in the module, _not_ the data after the C<__END__> token in the 'main'program, since the compiler encounters the 'require'd file later.=head2 SelfLoader autoloadingThe B<SelfLoader> works by the user placing the C<__DATA__>token I<after> perl code which needs to be compiled andrun at 'require' time, but I<before> subroutine declarationsthat can be loaded in later - usually because they may neverbe called.The B<SelfLoader> will read from the FOOBAR::DATA filehandle toload in the data after C<__DATA__>, and load in any subroutinewhen it is called. The costs are the one-time parsing of thedata after C<__DATA__>, and a load delay for the _first_call of any autoloaded function. The benefits (hopefully)are a speeded up compilation phase, with no need to loadfunctions which are never used.The B<SelfLoader> will stop reading from C<__DATA__> ifit encounters the C<__END__> token - just as you would expect.If the C<__END__> token is present, and is followed by thetoken DATA, then the B<SelfLoader> leaves the FOOBAR::DATAfilehandle open on the line after that token.The B<SelfLoader> exports the C<AUTOLOAD> subroutine to thepackage using the B<SelfLoader>, and this loads the calledsubroutine when it is first called.There is no advantage to putting subroutines which will _always_be called after the C<__DATA__> token.=head2 Autoloading and package lexicalsA 'my $pack_lexical' statement makes the variable $pack_lexicallocal _only_ to the file up to the C<__DATA__> token. Subroutinesdeclared elsewhere _cannot_ see these types of variables,just as if you declared subroutines in the package but in anotherfile, they cannot see these variables.So specifically, autoloaded functions cannot see packagelexicals (this applies to both the B<SelfLoader> and the Autoloader).The C<vars> pragma provides an alternative to defining package-levelglobals that will be visible to autoloaded routines. See the documentationon B<vars> in the pragma section of L<perlmod>.=head2 SelfLoader and AutoLoaderThe B<SelfLoader> can replace the AutoLoader - just change 'use AutoLoader'to 'use SelfLoader' (though note that the B<SelfLoader> exportsthe AUTOLOAD function - but if you have your own AUTOLOAD andare using the AutoLoader too, you probably know what you're doing),and the C<__END__> token to C<__DATA__>. You will need perl version 5.001mor later to use this (version 5.001 with all patches up to patch m).There is no need to inherit from the B<SelfLoader>.The B<SelfLoader> works similarly to the AutoLoader, but picks up thesubs from after the C<__DATA__> instead of in the 'lib/auto' directory.There is a maintenance gain in not needing to run AutoSplit on the moduleat installation, and a runtime gain in not needing to keep opening andclosing files to load subs. There is a runtime loss in needingto parse the code after the C<__DATA__>. Details of the B<AutoLoader> andanother view of these distinctions can be found in that module'sdocumentation.=head2 __DATA__, __END__, and the FOOBAR::DATA filehandle.This section is only relevant if you want to usethe C<FOOBAR::DATA> together with the B<SelfLoader>.Data after the C<__DATA__> token in a module is read using theFOOBAR::DATA filehandle. C<__END__> can still be used to denote the endof the C<__DATA__> section if followed by the token DATA - this is supportedby the B<SelfLoader>. The C<FOOBAR::DATA> filehandle is left open if anC<__END__> followed by a DATA is found, with the filehandle positioned atthe start of the line after the C<__END__> token. If no C<__END__> token ispresent, or an C<__END__> token with no DATA token on the same line, thenthe filehandle is closed.The B<SelfLoader> reads from wherever the currentposition of the C<FOOBAR::DATA> filehandle is, until theEOF or C<__END__>. This means that if you want to usethat filehandle (and ONLY if you want to), you should either1. Put all your subroutine declarations immediately afterthe C<__DATA__> token and put your own data after thosedeclarations, using the C<__END__> token to mark the endof subroutine declarations. You must also ensure that the B<SelfLoader>reads first by calling 'SelfLoader-E<gt>load_stubs();', or by using afunction which is selfloaded;or2. You should read the C<FOOBAR::DATA> filehandle first, leavingthe handle open and positioned at the first line of subroutinedeclarations.You could conceivably do both.=head2 Classes and inherited methods.For modules which are not classes, this section is not relevant.This section is only relevant if you have methods which couldbe inherited.A subroutine stub (or forward declaration) looks like sub stub;i.e. it is a subroutine declaration without the body of thesubroutine. For modules which are not classes, there is no realneed for stubs as far as autoloading is concerned.For modules which ARE classes, and need to handle inherited methods,stubs are needed to ensure that the method inheritance mechanism worksproperly. You can load the stubs into the module at 'require' time, byadding the statement 'SelfLoader-E<gt>load_stubs();' to the module to dothis.The alternative is to put the stubs in before the C<__DATA__> token BEFOREreleasing the module, and for this purpose the C<Devel::SelfStubber>module is available. However this does require the extra step of ensuringthat the stubs are in the module. If this is done I strongly recommendthat this is done BEFORE releasing the module - it should NOT be doneat install time in general.=head1 Multiple packages and fully qualified subroutine namesSubroutines in multiple packages within the same file are supported - but youshould note that this requires exporting the C<SelfLoader::AUTOLOAD> toevery package which requires it. This is done automatically by theB<SelfLoader> when it first loads the subs into the cache, but you shouldreally specify it in the initialization before the C<__DATA__> by puttinga 'use SelfLoader' statement in each package.Fully qualified subroutine names are also supported. For example, __DATA__ sub foo::bar {23} package baz; sub dob {32}will all be loaded correctly by the B<SelfLoader>, and the B<SelfLoader>will ensure that the packages 'foo' and 'baz' correctly have theB<SelfLoader> C<AUTOLOAD> method when the data after C<__DATA__> is firstparsed.=cut
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -