I think this discussion is pointless. You either provide an interface to your module---then you decide if it supports can()---or you implement an interface another module expects---then the author of that module decided if can() is needed. That's it.
Implementing a working can() isn't that hard. I'd say this should work (ATTN: untested, WILL contain syntax errors):
sub can {
my ($self, $what, $code) = (@_[0,1], undef);
return $code if $code = $self->UNIVERSAL::can($what);
return $code if $code = $self->_can($what);
foreach my $superclass (@ISA) {
return $code if $code = eval "\$self->${superclass}::can(\$wha
+t)";
}
return undef;
}
sub _can { # aka _load()
my ($self, $what) = @_;
if ($what eq 'foo') {
return sub {'foo'};
} else {
return undef;
}
}
sub AUTOLOAD {
my ($self, $code) = ($_[0], undef);
goto &$code if $code = $self->can($AUTOLOAD);
die "oops";
}
PS: This even provides a working way for using AUTOLOAD with multi-inheritance, I'd say.
-
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.
|