The problem with a source filter approach is that it can very easily run over program data or conflict with existing filters. Personally, I would've thought a straight-forward
import approach would've been easiest e.g
package allow_as;
use Carp 'croak';
sub import {
my($pkg, %args) = @_;
return
unless exists $args{as} and length $args{as};
croak "Symbol table '$args{as}' already exists"
if defined *{"$args{as}\::"};
*{"$args{as}\::"} = *{"$pkg\::"};
}
1;
=pod
=head1 USAGE
package Your::Very::Long::Name::Here;
use base 'allow_as';
sub import {
## perhaps you want your own import code?
$_[0]->SUPER::import(@_[1 .. $#_]);
}
## later
use Your::Very::Long::Name::Here (
as => 'yvlnh',
other => [qw/user parameters perhaps?/],
);
=cut
This doesn't work as globally as your filtering mechanism, but it also follows in the footsteps of
Exporter of allowing the user to simply inherit the module to enable aliasing (which may not always be desirable, like the ability to export random methods). Also, the reason I stuck with the aliasing route is that it is much cleaner than simply using
@ISA. It means that objects are
blessed into the original package and not the inherited alias, which will keep any introspection consistent, saves avoids dispatching every method call, and it really is an
alias as opposed to a quick work-around.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.