I had a little library which supported a number of
interfaces: procedural, class-based and object-based.
The _shift_self function called as
my $self = &_shift_self looks
at the caller's @_ and Does-What-I-Mean, possibly
shifting the first arg or returning a class name.
A bigger example will follow.
package MyClass;
use Scalar::Util qw(blessed);
sub _shift_self {
if(!defined $_[0]) {
return __PACKAGE__;
} elsif(blessed $_[0]
&& $_[0]->isa(__PACKAGE__) ) {
return shift;
} elsif ( $_[0] =~ /^[_a-zA-Z][\w:']*$/ # Legit package names
&& $_[0]->isa(__PACKAGE__) ) {
# should it be UNIVERSAL::isa($_[0],__PACKAGE); ??
return shift;
} else {
return __PACKAGE__;
}
}
sub new {
my $self = &_shift_self;
my $class = ref $self || $self;
return bless [1], $class;
}
sub dump_self {
my $self = &_shift_self;
print '$self is <',Dumper($self), '> ';
$self->do_something(@_);
}
-
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.
|